- Dec 20, 2023
-
-
0654051d CMakePresets.json: Don't use architecture and toolset if empty Acked-by:
Kitware Robot <kwrobot@kitware.com> Tested-by:
buildbot <buildbot@kitware.com> Merge-request: !9093
-
ca5a300d add_test: Honor CROSSCOMPILING_EMULATOR only when cross-compiling Acked-by:
-
d31b4881 Swift/Ninja: Fix missing OFM in CMP0157 OLD behavior Acked-by:
-
ab6b44b1 FindCURL: Fix parsing protocols/features from pkg-config output Acked-by:
-
d0ab70d5 Help: Fix typo in dependency provider method keyword Acked-by:
-
-
61436858 UsePkgConfig: Restore removal of trailing whitespace from pkg-config output Acked-by:
-
61436858 UsePkgConfig: Restore removal of trailing whitespace from pkg-config output Acked-by:
-
Kitware Robot authored
-
- Dec 19, 2023
-
-
Since commit f73a5bfa (UsePkgConfig: Replace exec_program() with execute_process(), 2023-07-24, v3.28.0-rc1~321^2~6), trailing whitespace was introduced into libraries linked, which violates CMP0004.
-
Kyle Edwards authored
Fixes: #24864
-
-
-
6d962f37 Help: Fix indentation level in fileapi docs for target attribute 'launchers' Acked-by:
-
2ea216a6 GoogleTest: Add working directory to gtest_discover_tests error message Acked-by:
-
dc509842 CMakePackageConfigHelpers: Clarify Apple platform selection usage error 3b958667 CMakePackageConfigHelpers: Clarify Apple platform selection template name Acked-by:
-
1a6303aa CMakePackageConfigHelpers: Fix generate_apple_platform_selection_file docs Acked-by:
-
-
defbfd6f Xcode: Restore support for standalone IMPORTED_LOCATION_<CONFIG> Acked-by:
-
defbfd6f Xcode: Restore support for standalone IMPORTED_LOCATION_<CONFIG> Acked-by:
-
Kitware Robot authored
-
- Dec 18, 2023
-
-
Evan Wilde authoredThe CMP0157 old behavior omitted the output-file-map after the Swift build split because we stopped calling `EmitSwiftDependencyInfo` when we could not split the build because we didn't call `WriteObjectBuildStatement`. If we can't split the build, then we still need to include the OFM information to not break incremental builds.
-
Brad King authored
Previously the documentation was not rendered correctly.
-
Brad King authored
`generate_apple_platform_selection_file` requires `INSTALL_DESTINATION`.
-
-
1dd4a9ba Tests: Cover generate_apple_platform_selection_file on all platforms 3148db45 CMakePackageConfigHelpers: Fix Apple platform selection for tvOS Acked-by:
-
In commit 878ae038 (macOS: IMPORTED framework: Honor SYSTEM target property in all cases, 2023-08-27, v3.28.0-rc1~162^2) we broke support for `IMPORTED_LOCATION_<CONFIG>` without `IMPORTED_CONFIGURATIONS`. Previously it worked if the importing project's configurations match the set of `IMPORTED_LOCATION_<CONFIG>` properties set. Fix that case. Fixes: #25506 Issue: #25515
-
If the working directory didn't exist, the old message just says: Error running test executable. Path: '<Path to test executable>' Result: No such file or directory Output: This leads the user to the conclusion that the test executable doesn't exist, which isn't true. Make the true cause visible by reporting the working directory in the error message. -
-
Kitware Robot authored
-
- Dec 17, 2023
-
-
04153049 FetchContent: Fix FIND_PACKAGE_ARGS not being passed to dep providers Acked-by:
-
18c514a8 Help: Add note not to use FETCHCONTENT_FULLY_DISCONNECTED on first run Acked-by:
-
ba5882a6 Help: Document Xcode project visibility constraints for embedding Acked-by:
-
Kitware Robot authored
-
- Dec 16, 2023
-
-
9bed4f4d Swift/Ninja: Split compilation model 64b33678 cmGlobalGenerator: Allow passing language to GetLangaugeOutputExtension Acked-by:
-
Brad King authored
The test added by commit 37bc3400 (CMakePackageConfigHelpers: Add generate_apple_platform_selection_file(), 2023-11-03) covers importing only on macOS, and is specific to the xcframework test case. Add a dedicated test for `generate_apple_platform_selection_file` that covers export and import on all platforms.
-
Craig Scott authored
Fixes: #25481
-
Craig Scott authored
Fixes: #25504
-
Kitware Robot authored
-
- Dec 15, 2023
-
-
Craig Scott authored
The cmake.vim file is generated by scanning for keyword-like strings in the docs. Update the corresponding wrong entry there too directly for now, which will fix the wrong entry until the next full regeneration of the file. Fixes: #25503
-
