- Mar 02, 2020
-
-
Brad King authored
-
- Feb 28, 2020
-
-
c794b70f Ninja Multi-Config: Always generate build.ninja 9590c3a4 Generator: Don't allow Ninja Multi-Config variables on other generators 7a63dafa Ninja Multi-Config: Remove "NMC" from variable names Acked-by: Kitware Robot <kwrobot@kitware.com> Merge-request: !4403
-
185d1aef foreach: Set fatal error on invalid range a33b3949 foreach: Fix crash when parsing invalid integer Acked-by: Kitware Robot <kwrobot@kitware.com> Merge-request: !4407
-
426941c4 Autogen: Recognize the new Q_NAMESPACE_EXPORT macro in AUTOMOC Acked-by: Kitware Robot <kwrobot@kitware.com> Merge-request: !4398
-
- Feb 27, 2020
-
-
Kyle Edwards authored
Fixes: #20394
-
Kyle Edwards authored
Fixes: #20393
-
Kyle Edwards authored
If CMAKE_DEFAULT_BUILD_TYPE is not specified, use the first item from CMAKE_CONFIGURATION_TYPES instead.
-
We may want to enable these variables later on with specific semantics. To avoid breaking backwards compatibility, make it an error to use them for now.
-
Also rename `..._DEFAULT_BUILD_FILE_CONFIG` to `..._DEFAULT_BUILD_TYPE`. These name changes make the variables meaningful for future use by other generators.
-
7e9b9fe9 PCH: Copy the timestamp from an absolute header file Acked-by: Kitware Robot <kwrobot@kitware.com> Merge-request: !4400
-
06702acb KWSys: Terminal: Add st-256color to VT100 color support whitelist Acked-by: Kitware Robot <kwrobot@kitware.com> Merge-request: !4394
-
42c6a1bf FindPython: Do not cache computed result variables a7b4516e FindPython: Mark non-public cache entries INTERNAL Acked-by: Kitware Robot <kwrobot@kitware.com> Merge-request: !4393
-
- Feb 26, 2020
-
-
3bff8397 Help: Clarify that the CTest resource allocation feature doesn't oversubscribe Acked-by: Kitware Robot <kwrobot@kitware.com> Merge-request: !4401
-
If `target_precompile_headers` contains a file from the project, then CMake will set the timestamp for `cmake_pch.h|xx` from that file. This helps with ccache and precompile headers. Fixes: #19923
-
Kyle Edwards authored
-
Since commit 06d9e67f (FindPython: Add capability to specify directly artifacts, 2019-08-15, v3.16.0-rc1~157^2) we accidentally add the result variables `Python*_LIBRARY_RELEASE` and `Python*_LIBRARY_DEBUG` to the cache. They are always computed from other results and so should not be presented to users in cmake-gui and ccmake to edit. Issue: #20362
-
Since commit 06d9e67f (FindPython: Add capability to specify directly artifacts, 2019-08-15, v3.16.0-rc1~157^2) we accidentally expose cache entries named `_Python...` to users in cmake-gui and ccmake. Mark those entries as `INTERNAL` to hide them. Issue: #20362
-
853c3eac Help: Note that CMAKE_CFG_INTDIR is not fully supported on Ninja Multi-Config Acked-by: Kitware Robot <kwrobot@kitware.com> Merge-request: !4397
-
95dbcf05 Tests: fix RunCMake.Make test when run on systems with non-english locale Acked-by: Kitware Robot <kwrobot@kitware.com> Merge-request: !4389
-
Set `LANG=C` in the environment so the output of `make` is predictable. Fixes: #19689
-
cc4e3048 Tests: Fix CFBundleTest for Ninja Multi-Config bcf4da52 Tests: Fix CustComDepend test for Ninja Multi-Config Acked-by: Kitware Robot <kwrobot@kitware.com> Merge-request: !4396
-
Qt 5.14 introduced a new moc keyword `Q_NAMESPACE_EXPORT`. Qt-Issue: https://bugreports.qt.io/browse/QTBUG-68014
-
- Feb 25, 2020
-
-
Kyle Edwards authored
-
-
-
Brad King authored
Backport KWSys commit `44eaaa6e8` (Terminal: Add st-256color to VT100 color support whitelist, 2020-02-19) to CMake 3.17.
-
a5be3916 CTest: Provide more detailed information on resource allocation error f0df3ed5 Refactor: Provide more detailed error information from TryAllocateResources() f1c34443 CTest: Improve error reporting with bad working directory for tests 1dec3594 Refactor: Require detail when calling cmCTestRunTest::StartFailure() Acked-by: Kitware Robot <kwrobot@kitware.com> Merge-request: !4390
-
b9d67447 FindCUDA: Only depend on Threads::Threads on platforms that need it Acked-by: Kitware Robot <kwrobot@kitware.com> Merge-request: !4377
-
c3e0d1ff FindPkgConfig: set policies CMP0054 and CMP0057 to new Acked-by: Kitware Robot <kwrobot@kitware.com> Merge-request: !4388
-
7da2c8c5 Merge branch 'backport-cuda-non-device-link' 738f3f23 Ninja: Do not use nvcc response files with non-nvcc tools Acked-by: Kitware Robot <kwrobot@kitware.com> Acked-by: Robert Maynard <robert.maynard@kitware.com> Merge-request: !4376
-
- Feb 24, 2020
-
-
Kyle Edwards authored
-
Kyle Edwards authored
-
Kyle Edwards authored
-
Kyle Edwards authored
-
In commit 46371132 (FindCUDA: CUDA_LIBRARIES doesn't contain raw `-pthread`, 2019-11-11, v3.17.0-rc1~455^2) we introduced use of the `Threads::Threads` target, but we do not `find_package(Threads)` on all platforms. Use the target only if it exists.
-
Brad King authored
-
Since commit d91b5a72 (Ninja: Add support for CUDA nvcc response files, 2019-05-30, v3.15.0-rc1~8^2) we use NVCC's `--options-file` option to avoid long link command lines via a response file. However, for non-device linking the host tools are used and the option does not make sense. Update the logic to use `--options-file` only for device linking. Linking with the host tools already has its own logic for response files. Fixes: #19954
-
5c6d6ec2 PCH: Clang: Update PCH usage flags to include original header Acked-by: Kitware Robot <kwrobot@kitware.com> Merge-request: !4360
-
Add an additional include flag to PCH usage command line to fix programs that rely on `compile_commands.json` file. Pass it to the preprocessor directly to avoid compiler driver to change it to '-include-pch'. When preprocessor is requested to preprocess a file, it tries to get the original filename from '.pch' and uses that file for preprocessing. CMake generates a '.pch' file from the '.hxx' file by passing an empty '.cxx' source file to the compiler as a compilation unit and the header file with the '-include' flag. After that, compiler puts compilation unit filename in the '.pch' as the original filename. However, CMake build system uses empty file as the source file and passes the header file using '-include-pch' flag. As a result, Clang uses the wrong file for preprocessing and produces the corrupted preprocessed file. Fixes: #20355 Signed-off-by: Sergey Larin <cerg2010cerg2010@mail.ru>
-
Rolf Eike Beer authored
One may encounter warnings if FindPkgConfig is used in any project, even indirectly, that has set any of these policies to old explicitely or requires an older version.
-