| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
| |
The legacy non-Clang variant seems to support a GNU-like extensions mode, which
is the default. Enable detection for it.
|
|\
| |
| |
| |
| |
| |
| | |
6a0ce19ce1 FortranCInterface: Fix compatibility with GCC gfortran 12 LTO
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !6879
|
|/
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Since version 12.0 the GCC Fortran compiler has implemented "WG5/N1942",
which causes, if link-time opmization is enabled, obfuscation of hard-coded
string values in the compiler objects and its resulting ELF-binaries.
This causes the CMake-internal detection of the mangling scheme for the
naming of subroutines to fail. Thus we must ensure to have any link-time
optimization features to be disabled on the executable file we perform the
detection on.
The static libraries, however, must be build with LTO and non-LTO objects,
as that will ensure the verify step will operate on IPO objects, if building
those is requested by the system compiler flags.
Fixes: #23123
Signed-off-by: Björn Esser <besser82@fedoraproject.org>
|
|\ |
|
| |\
| | |
| | |
| | | |
Merge-request: !6858
|
|\ \ \
| | |/
| |/|
| | |
| | |
| | |
| | | |
9e24437c91 VS: Remove the '/guard:cf' flag from v143 link flag table
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !6858
|
| |/
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Apply the change from commit db35e3cfd6 (VS: Fix support for '/guard:cf'
linker flag for v142, 2019-01-24, v3.14.0-rc1~74^2~2) to the v143 flag
table.
The entry for `LinkControlFlowGuard` in `v143_Link.json` does not work
when used in a `.vcxproj` file. Drop our link flag table entries for
this toolset so that the flag will be passed via `AdditionalOptions`.
Also add a test case.
|
|\ \
| | |
| | |
| | |
| | |
| | |
| | | |
3a8b6653dc MSVC: Use -external:I flag without space to support Clang tools
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !6855
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Since commit f29e1874ad (Compiler/MSVC: use the `-external:I` flag for
system includes, 2020-05-19, v3.22.0-rc1~593^2) we use the new flag
followed by the include directory as a separate argument. Some versions
of `clang-cl` and `clang-tidy` do not support the flag unless the
include directory is attached to it, so use that form instead.
Fixes: #22979
|
|\ \ \
| |/ /
|/| |
| | |
| | |
| | |
| | |
| | | |
41bebbe50a file: Restore error capture in undocumented READ_ELF mode
Acked-by: Kitware Robot <kwrobot@kitware.com>
Acked-by: buildbot <buildbot@kitware.com>
Merge-request: !6853
|
|/ /
| |
| |
| |
| |
| |
| |
| |
| | |
Revise the error message added by commit 115ff6a347 (cmELF: Include the
ELF parsing code unconditionally, 2021-06-17, v3.22.0-rc1~557^2) to
honor the `CAPTURE_ERROR` option. This is needed by the call site in
`BundleUtilities` to suppress errors on non-ELF files.
Fixes: #23074
|
|\ \
| | |
| | |
| | |
| | |
| | |
| | | |
c2777ed008 ASM: Fix identification of armasm 6.17+
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !6833
|
|/ /
| |
| |
| | |
Spelling of "ARM Compiler" changed to "Arm Compiler".
|
|\ \
| | |
| | |
| | |
| | |
| | |
| | | |
85a07b4b49 ci: Explicitly disable Java tests on VS builds
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !6826
|
|/ /
| |
| |
| |
| | |
Extend the change from commit 840fa28d3d (ci: Explicitly disable Java
tests on Windows, 2021-12-16) to cover VS builds too.
|
|\ \
| | |
| | |
| | |
| | |
| | |
| | | |
d45667d459 FindBoost: Do not warn about now-supported version 1.78
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !6819
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
In commit d176ff71c0 (FindBoost: Add support for Boost 1.78, 2021-12-15)
we forgot to update the future-version check.
Issue: #23016
|
|\ \ \
| |/ /
|/| |
| | |
| | |
| | |
| | | |
ae6b25d920 FindGLUT: Provide legacy GLUT_INCLUDE_DIR result in pkg-config code path
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !6814
|
|/ /
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Since commit f90d15458a (FindGLUT: Use pkg-config to find flags if
available, 2021-06-11, v3.22.0-rc1~469^2) we return early if pkg-config
provides the information. During review of that commit, code to
populate the legacy `GLUT_INCLUDE_DIR` result variable was removed from
that code path. Add code to provide it.
Also fix the test case to use `GLUT_INCLUDE_DIR`, the result variable
documented officially by the module.
Fixes: #23018
|
|\ \
| | |
| | |
| | |
| | |
| | |
| | | |
d4bb6c0c7f FindBoost: Add support for Python 3.10
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !6809
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Regexps in FindBoost assumed that python's minor version had only one
digit. That became not true for 3.10.
Fixes: #23025
|
|\ \ \
| | |/
| |/| |
|
| |\ \
| | | |
| | | |
| | | | |
Merge-request: !6806
|
|\ \ \ \
| | |/ /
| |/| /
| |_|/
|/| |
| | |
| | | |
612c0d49f4 VS: Fix detecting icx.exe with Intel Compiler toolsets newer than 2021
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !6806
|
| |/
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The logic added by commit 7808cbd644 (CMakeDetermineCompilerId: support
Intel DPC++ compiler toolset for VS gen, 2020-12-06, v3.20.0-rc1~330^2)
matches a specific toolset known to be the `icx.exe` compiler, and
assumes all other Intel C++ compilers (that are not DPC++) must be
`icl.exe`.
Since `icx.exe` is officially replacing `icl.exe`, use a regex that
matches the now-fixed set of toolsets known to use `icl.exe`. Any other
Intel C++ compiler will be assumed to be `icx.exe`.
Signed-off-by: William R. Dieter <william.r.dieter@intel.com>
|
|\ \
| | |
| | |
| | |
| | |
| | |
| | | |
840fa28d3d ci: Explicitly disable Java tests on Windows
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !6807
|
|/ /
| |
| |
| |
| |
| |
| | |
Avoid searching for a Java installation on Windows hosts.
This will allow some CI hosts to have Java for other projects.
We already do this on macOS. While at it, clarify the macOS setting.
|
|\ \
| | |
| | |
| | |
| | |
| | |
| | | |
d176ff71c0 FindBoost: Add support for Boost 1.78
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !6804
|
|/ /
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Update the list of known versions.
Run the command
cmake -DBOOST_DIR=/path/to/boost_1_78_0 \
-P Utilities/Scripts/BoostScanDeps.cmake
to extract dependencies from the 1.78.0 source tree.
The dependencies differ from those of 1.77:
* The `log` component no longer depends on `date_time`.
Fixes: #23016
|
|\ \
| | |
| | |
| | |
| | |
| | |
| | | |
38b00f8801 Android: Fix linking android_support for pre-21 system STL
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !6799
|
|/ /
| |
| |
| |
| |
| |
| | |
This typo was introduced in commit 4dca078829 (Android: Link c++abi and
android_support when necessary, 2020-10-29, v3.20.0-rc1~541^2).
Fixes: #23004
|
|\ \
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
43844c5d82 FindPython: Add support for Python 3.11
Acked-by: Kitware Robot <kwrobot@kitware.com>
Acked-by: Marc Chevrier <marc.chevrier@gmail.com>
Merge-request: !6792
|
|/ / |
|
| | |
|
|\ \
| | |
| | |
| | |
| | |
| | |
| | | |
bed4b1583e Utilities/Release: Add script to sign/notarize macOS application bundle
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !6784
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
We produce macOS binaries for `cmake.org` using GitLab CI jobs.
Binaries for official releases are additionally signed and notarized
manually by a maintainer with suitable signing certificates and Apple
developer account credentials. Add a script to drive these steps.
|
|\ \ \
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
b59f7600c4 HIP: Enable CMAKE_EXPORT_COMPILE_COMMANDS for HIP
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !6789
|
| | | |
| | | |
| | | |
| | | | |
Fixes: #22986
|
|\ \ \ \
| |/ / /
|/| | |
| | | |
| | | |
| | | |
| | | | |
d4ba945c48 CMakeParseLibraryArchitecture: Fix parsing /lib/<arch> implicit object path
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !6790
|
|/ / /
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
The current regular expression is able to match `/usr/lib/<arch>`,
`/usr/usr/lib/<arch>`, `/usr/usr/usr/lib/<arch>`, ... but not
`/lib/<arch>`.
This behavior ends up causing the detected architecture to
be x86_64-pc-linux-gnu when the Clang compiler is installed on
a "non-system" location (like /opt/llvm-13) which, in turn, makes
almost every 'find_library()' fail because the correct
architecture is x86_64-linux-gnu.
This is due to a typo in commit 764606e256 (CMakeDetermineCompilerABI:
Extract lib arch from implicit object file paths, 2021-04-05,
v3.20.1~10^2), which used `+` instead of `?`.
|
|\ \ \
| |/ /
|/| |
| | |
| | |
| | |
| | | |
69419c5870 ci: Enable more VS tests that use managed code
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !6782
|
|/ /
| |
| |
| |
| |
| |
| | |
A couple of VS tests were conditioned on `NOT CMAKE_GENERATOR_TOOLSET`,
but in CI jobs with VS we always set `CMAKE_GENERATOR_TOOLSET`. Make
the condition specific to excluding the `v90` toolset, which was its
original intention anyway.
|
|\ \
| | |
| | |
| | |
| | |
| | |
| | | |
13a7ae2194 VS: Revert "Add missing label in C# project-build events"
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !6781
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Revert commit b284a21fee (VS: Add missing label in C# project-build
events, 2021-09-03, v3.22.0-rc1~156^2). The change broke cases using
multiple successful custom commands. Revert it pending further
investigation into the interaction of the generated script code with
`Microsoft.Common.CurrentVersion.targets`, and whether this is needed
for all managed projects or just C# projects.
Also add a test covering the case that was broken.
Fixes: #22964
Issue: #21440
|
|\ \ \
| |/ /
|/| |
| | |
| | |
| | |
| | | |
90a49647e9 FindPkgConfig: Restore finding pkg-config before pkgconf
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !6780
|
|/ /
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Since commit 94a84dc0af (FindPkgConfig: add pkgconf to the search list.,
2021-07-02, v3.22.0-rc1~468^2), `pkgconf` is preferred over `pkg-config`
if they appear in the same directory. In some environments,
`pkg-config` may be a wrapper that adds semantics beyond either
`pkgconf` or the normal `pkg-config`. Prefer `pkg-config` over
`pkgconf` in order to preserve the prior behavior in such environments.
Fixes: #22976
|
|\ \
| | |
| | |
| | |
| | |
| | |
| | | |
a35bf772de FindPython: clarify static libraries hint usage
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !6772
|
| | |
| | |
| | |
| | | |
Fixes: #22956
|
|\ \ \
| |/ /
|/| |
| | |
| | |
| | |
| | |
| | |
| | | |
643fc46bdc file(RPATH): Restore tolerance of unknown formats if new RPATH is empty
5596cba7dc cmSystemTools: Remove unnecessary mark-as-used casts to void
Acked-by: Kitware Robot <kwrobot@kitware.com>
Acked-by: buildbot <buildbot@kitware.com>
Merge-request: !6779
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Since commit 2e1149874d (cmSystemTools: Support multiple binary formats,
2021-06-14, v3.22.0-rc1~575^2) the `file(RPATH_...)` operations fail on
files that are not ELF or XCOFF format. Previously the RPATH operations
tolerated files of unknown format if the goal was to produce a file with
an empty RPATH. Restore this tolerance in order to support setting an
empty RPATH on GNU ld scripts.
Fixes: #22963
|