diff options
| author | Brad King <brad.king@kitware.com> | 2025-04-02 13:27:27 (GMT) |
|---|---|---|
| committer | Brad King <brad.king@kitware.com> | 2025-04-09 21:06:13 (GMT) |
| commit | 2e59cee9225f1a698d3f6cf537dc32675dc56fb8 (patch) | |
| tree | c37b05880a777b1fbe7bee78b948d1df6202a8fd /Utilities/cmcppdap/src/jsoncpp_json_serializer.cpp | |
| parent | c653c1aa475d746f135b2d3defd6bc61279b2ea1 (diff) | |
| download | CMake-2e59cee9225f1a698d3f6cf537dc32675dc56fb8.zip CMake-2e59cee9225f1a698d3f6cf537dc32675dc56fb8.tar.gz CMake-2e59cee9225f1a698d3f6cf537dc32675dc56fb8.tar.bz2 | |
FindXCTest: Fix test module generation for Xcode 16
In Xcode 7.3 and above, the `TEST_HOST` setting causes Xcode to
implicitly place the test module inside the executable bundle regardless
of the module's own location settings. Since commit a364d2513a (Xcode:
Fixup XCTest bundle location for Xcode 7.3, 2016-03-25, v3.5.2~6^2) we
explicitly tell CMake to put the test module in the same location so
that generator expressions used by `xctest_add_test` agree with where
Xcode actually puts it. In Xcode 16 and above, our explicit location
settings for the test module conflict with Xcode's `TEST_HOST` rules,
causing errors about multiple commands producing the same path.
Fix this by dropping CMake's explicit location for the test module
unless needed to match a project-specified location for the testee.
Instead, teach `xctest_add_test` to express the xctest module location
selected by `TEST_HOST` by using generator expressions referencing the
testee bundle.
Fixes: #26301
Fixes: #26514
Diffstat (limited to 'Utilities/cmcppdap/src/jsoncpp_json_serializer.cpp')
0 files changed, 0 insertions, 0 deletions
