- Feb 23, 2021
-
-
Brad King authored
The upstream release includes binaries for the architectures we need. However, the binaries do not have execute permission in their tarballs, so add it explicitly.
-
Brad King authored
It is a universal binary for both `x86_64` and `arm64` architectures.
-
74fe16a2 Tests: Fix ExternalProject CONFIGURE_HANDLED_BY_BUILD on 1s filesystems Acked-by:
Kitware Robot <kwrobot@kitware.com> Merge-request: !5838
-
1c15eb39 Tests: Suppress failures on macOS arm64 due to separate Xcode signing phase 92418ac0 Tests: Fix CTestTestCrash expected output on macOS arm64 8b22d9b3 Tests: Remove explicit no-signing marks from BundleTest 483db3de Tests: Clarify internal project name in RunCMake.GoogleTest cases Acked-by:
-
134d6912 cmake-gui: Restore search bar for cache view and environment dialog Acked-by:
-
ec030877 NAG: Fix using Fortran modules from their output directory Acked-by:
-
a3df25c6 Autogen: Don't change the order of HEADERS array in AutogenInfo.json Acked-by:
-
- Feb 22, 2021
-
-
Brad King authored
Some tests fail because Xcode runs `POST_BUILD` commands before signing the binaries they run. Tell the linker to perform ad-hoc codesign even though Xcode normally tells it not to. Other tests fail because `install_name_tool` does not revise ad-hoc signatures without the codesign `linker-signed` flag. Add that flag ourselves where needed by our tests. For now these changes help our test suite pass so we can use it to cover everything else. Both of these cases may need further investigation to update CMake to help projects in general. Issue: #21845, #21854
-
This was broken by commit f1de6f66 (cmake-gui: Support building against Qt6, 2020-12-17, v3.20.0-rc1~205^2~7). Fixes: #21850
-
Brad King authored
-
Brad King authored
These were added by commit e29a92f5 (Xcode: Make BundleTests compatible with Xcode 11, 2019-09-01, v3.16.0-rc1~158^2). The real problem is that the `.app` is constructed with text files under the `.app/Contents/MacOS/` folder. Move those, and drop the special no-signing configuration.
-
Brad King authored
-
Following commit 7155e358 (ExternalProject: Add CONFIGURE_HANDLED_BY_BUILD option, 2020-12-16, v3.20.0-rc1~168^2), modify the CONFIGURE_HANDLED_BY_BUILD test to sleep 1.125 seconds to make sure the file timestamp is always updated regardless of the resolution of the underlying filesystem. Fixes: #21830
-
b0da6712 FetchContent: Don't update timestamps if files don't change 404cddb7 ExternalProject: Fix misuse of IS_NEWER_THAN in timestamp checks Acked-by:
-
The refactoring in 17e5516e (FetchContent: Invoke steps directly and avoid a separate sub-build, 2021-01-29) uses a different way of writing out the step scripts and updating time stamps when steps are executed. That inadvertently always wrote out the scripts for custom commands, even when the contents didn't change. This caused their timestamp to always be updated, resulting in those steps always being seen as out-of-date and needing to be re-executed. The way timestamps were checked to determine whether to re-execute a step also did not adequately account for file systems which only have second-resolution timestamps. The IS_NEWER_THAN if condition also returns true when timestamps are the same, so one needs to use the negative form to get a true "is newer than" test. ExternalProject is not susceptible to this problem because it uses file(GENERATE) to write out the script files and that only updates the file's timestamp if the contents change. It also mostly leaves timestamp checking to the build tool.
-
When using a file system which only has second resolution timestamps, there is a reasonably high likelihood of timestamps being the same. The IS_NEWER_THAN test returns true when timestamps are the same, so don't redo downloads when they match exactly.
-
9945b3b5 VS: Restore support for PCH in CXX but not C within once target d9fd32b3 cmVisualStudio10TargetGenerator: Refactor per-source PCH logic Acked-by:
-
90c2f138 CPackIFWInstaller: Avoid potential null pointer dereference Acked-by:
-
cf9a7187 Help: Fix CPACK_DEBIAN_PACKAGE_SHLIBDEPS_PRIVATE_DIRS documentation Acked-by:
-
Brad King authored
The NAG Fortran compiler's `-mdir` flag sets the module output directory but does not add the directory to the search path for using modules. This is inconsistent with other compilers like the GNU Fortran compiler's `-J` flag that does both. In order to make these consistent, add the module output directory with a `-I` flag on the NAG Fortran compiler so that it will be searched when using modules too. We already do this for the XL Fortran compiler since commit 210b0b99 (XL: Fix using Fortran modules from their output directory, 2020-02-28, v3.18.0-rc1~640^2~1).
-
Craig Scott authored
Qt6 reads our internal AutogenInfo.json file. In 92d7b456 (Autogen: Add support for per-config sources, 2020-10-20), the ordering of the HEADERS array elements was changed and this broke their cmake_automoc_parser. We don't need to change the order of the array elements, we can append to the existing ones instead. Do this to allow their cmake_automoc_parser to continue to work. Fixes: #21823
-
- Feb 19, 2021
-
-
-
Brad King authored
De-duplicate the link language lookup.
-
Brad King authored
-
c9244f36 IntelLLVM: Make explicit Fortran preprocessing under Ninja more robust 056d4bf5 Merge branch 'backport-intel-fortran-preprocess' af074c26 Intel: Make explicit Fortran preprocessing under Ninja more robust Acked-by:
-
87b170d9 Help: Add build and test preset to examples in cmake-presets(7) 3f8cf006 Help: Clarify preset name conflict rules in cmake-presets(7) Acked-by:
-
06e50776 bindexplib: remove stray debugging output when using llvm-nm Acked-by:
Ben Boeckel <ben.boeckel@kitware.com> Merge-request: !5828
-
-
Craig Scott authored
In d1683032 (CPackIFW: Improve warning and docs for show page list option, 2021-02-14), code was added to report the current QtIFW version. That code didn't check that there was a Generator object before using it, resulting in a scanbuild warning about a potential null pointer dereference. Add a check and output a more general warning message if we don't have the current QtIFW version available to report.
-
- Feb 18, 2021
-
-
22140f7a Help: Add internal links to if() docs Acked-by:
-
Co-Author: Brad King <brad.king@kitware.com>
-
-
8f1e607e Help: Document JSON comment support in cmake-presets(7) Acked-by:
-
47ab2d4d Help: Clarify role of binaryDir inheritance in cmake-presets(7) 0e3c361f Help: Link to tool-specific preset arguments from cmake-presets(7) dd6165fb Help: Mention version 2 in cmake-presets(7) cdbd1ae6 Utilities/Sphinx: Avoid converting -- to an en-dash Acked-by:
-
-
Brad King authored
Suggested-by: Michael Hirsch
-
Brad King authored
Fixes: #21835
-
Brad King authored
Version 2 is required for build and test presets. Fixes: #21829
-
Brad King authored
-
-
