- Feb 11, 2021
-
- Feb 05, 2021
-
-
Brad King authored
Merge-request: !5776
-
Brad King authored
In commit f034b0f6 (CMake compilation: do not use compiler extensions, 2020-03-14, v3.18.0-rc1~494^2) we explicitly defined `_POSIX_C_SOURCE` to ensure availability of POSIX APIs even when compiler extensions are not enabled. Update the code to avoid redefining `_POSIX_C_SOURCE` if it is already defined. This occurs when building our release binaries as configured in `Utilities/Release/linux`, where we define `_POSIX_C_SOURCE` explicitly on the compiler command line.
-
- Jan 21, 2021
- Dec 14, 2020
-
-
Brad King authored
Merge-request: !5614
-
Brad King authored
Remove the `cleandead` tool invocation added by commit fb182159 (Ninja: clean ninja metadata once generated, 2019-05-13, v3.17.0-rc1~207^2). The tool deletes files that were not previously deleted by regenerating the build system. Also, there are use cases where no-longer-generated files should not be removed, such as Qt's TS files. Fixes: #21549
-
- Dec 07, 2020
-
-
Brad King authored
Merge-request: !5574
-
- Dec 04, 2020
-
-
Ben Boeckel authored
Commit 951640f1 (FindPython: manage SOABI for all Python versions, 2020-08-11) extended support for Python2's SOABI variable in order to support the PyPy interpreter as well. This caused a regression in the way that the SOABI variable was built up for the CPython interpreter. This caused the variable to be set to `.so` which ended up causing a doubling of the resulting `SOABI` variable in the end. Co-Author: Marc Chevrier <marc.chevrier@gmail.com> Fixes: #21548
-
- Nov 25, 2020
-
-
Brad King authored
Merge-request: !5531
-
If the user specifies CMAKE_CUDA_ARCHITECTURES we use those during detection and error out if they don't work. For Visual Studio a dummy project file is used instead of invoking the compiler directly. NVCC would thus use its default and we'd fail if CMAKE_CUDA_ARCHITECTURES was anything other than NVCC's default. Use the necessary project file variable in CMakeDetermineCompilerId.cmake to match other generators. Fixes #21492.
-
- Nov 18, 2020
-
- Nov 12, 2020
-
-
Brad King authored
Merge-request: !5506
-
Brad King authored
When targeting a platform that supports multiple architectures, Xcode may choose to build all of them in our small compiler id project. Update the regex we use to extract the path to the compiler from the Xcode output to account for this. Fixes: #21425
-
- Oct 27, 2020
-
-
Brad King authored
Merge-request: !5434
-
Brad King authored
Since commit e672db62 (FindRuby: Rename variables to match case of module name, 2020-03-11, v3.18.0-rc1~546^2), the result variables named with the old `RUBY_` prefix are provided by compatibility code that maps from the new `Ruby_` prefix variables. This variable was accidentally left out. Fixes: #21369
-
Brad King authored
Merge-request: !5422
-
In the following scenario (with 3.18 policies): 1. A CXX target is created. 2. CUDA language is enabled. CMake 3.18 introduced CMP0104, which requires CUDA_ARCHITECTURES to be set. Because the CXX target was created before CUDA was enabled it wouldn't have it set. The Visual Studio generator would however end up computing CUDA compile options for the CXX target, which would result in a fatal error due to the policy violation. There doesn't seem to be a reason to do this for targets that don't actually use the CUDA language, so we can skip and generate the CXX target just fine. Fixes: #21341
-
- Oct 26, 2020
-
-
Brad King authored
Merge-request: !5430
-
Kyle Edwards authored
-
- Oct 15, 2020
-
-
Brad King authored
Merge-request: !5364
-
- Oct 14, 2020
- Oct 06, 2020
-
-
8d87cfdb VS: Fix regression in C# source links Acked-by:
Kitware Robot <kwrobot@kitware.com> Merge-request: !5314
- Oct 05, 2020
-
- Sep 30, 2020
-
-
8a2977ba OBJCXX: Fix regression for compiling cpp files as objcxx Acked-by:
Kitware Robot <kwrobot@kitware.com> Merge-request: !5296
-
5f6b0ba8 FindCUDA/select_compute_arch: Add CUDA 11.1 and SM86 support Acked-by:
Kitware Robot <kwrobot@kitware.com> Merge-request: !5292
-
- Sep 29, 2020
-
-
In commit 8d61294c (PCH: Mark CMake PCH source files as -x <lang>-header, 2020-09-04, v3.18.3~14^2) we removed the explicit `-x objective-c++` flag. This broke cases with custom source extensions. Restore the explicit `-x objective-c[++]` flag and put it before the `<FLAGS>` placeholder. The latter will contain the proper `-x objective-c[++]-header` value and will override the `-x objective-c[++]` value set before. Fixes: #21234
-
b11c7236 VS: Populate `std:c{11,17}` flag table entries for v142 Acked-by:
Kitware Robot <kwrobot@kitware.com> Acked-by:
Raul Tambre <raul@tambre.ee> Merge-request: !5290
-
-
- Sep 28, 2020
-
-
696d16ae FindJNI: Add aarch64 support Acked-by:
Kitware Robot <kwrobot@kitware.com> Acked-by:
Vitaly Lipatov <lav@etersoft.ru> Merge-request: !5275
- Sep 25, 2020
-
-
f5d3da09 Clang: Look for llvm-lib when using MSVC-like front-end Acked-by:
Kitware Robot <kwrobot@kitware.com> Acked-by:
Thomas Bernard <thomas@famillebernardgouriou.fr> Merge-request: !5264
-
- Sep 24, 2020
-
-
In commit 55196a14 (MSVC: Use 'lib' instead of 'link /lib' to create static libraries, 2020-01-10, v3.18.0-rc1~625^2) we changed CMake to use lib instead of `link /lib` to create static libraries, but it didn't search for `llvm-lib`. If you have `llvm-lib` but not `lib` (e.g. when cross-compiling), when `CMakeFindBinutils` is invoked for the `C` and `CXX` languages, `CMAKE_AR` is not found. When it's subsequently invoked for the ASM language, `CMAKE_ASM_SIMULATE_ID` and `CMAKE_ASM_COMPILER_FRONTEND_VARIANT` are not set (because `CMakeDetermineASMCompiler` doesn't call `CMAKE_DETERMINE_COMPILER_ID`, which sets those variables), so we go down the non-MSVC conditional and set `CMAKE_AR` to a GNU-style `ar`, which of course does not understand lib flags. Explicitly search for `llvm-lib` to avoid this situation.
-
6c094c1c FindPython: Fix erroneous regex in ABI check Acked-by:
Kitware Robot <kwrobot@kitware.com> Merge-request: !5257
-
- Sep 23, 2020
-
-
A regex added by commit 6fdfe242 (FindPython: enhance ABI checks against include directory, 2020-09-02, v3.18.3~17^2) was missing a backslash. Fixes: #21223
-