mirror of
https://github.com/Kitware/CMake.git
synced 2026-01-03 20:29:56 -06:00
2e59cee922
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
30 lines
888 B
CMake
30 lines
888 B
CMake
enable_language(Swift)
|
|
|
|
set(CMAKE_XCODE_ATTRIBUTE_CODE_SIGNING_REQUIRED NO)
|
|
set(CMAKE_XCODE_ATTRIBUTE_CODE_SIGN_IDENTITY "")
|
|
set(CMAKE_TRY_COMPILE_TARGET_TYPE STATIC_LIBRARY)
|
|
|
|
find_package(XCTest REQUIRED)
|
|
|
|
add_executable(TestedApp MACOSX_BUNDLE dummy_main.swift)
|
|
|
|
xctest_add_bundle(TestingAppBundle TestedApp dummy_main.swift)
|
|
|
|
macro(add_test NAME name COMMAND xctest arg)
|
|
set(actual_arg "${arg}" PARENT_SCOPE)
|
|
endmacro()
|
|
|
|
xctest_add_test(TestedApp.TestingAppBundle TestingAppBundle)
|
|
|
|
if(NOT DEFINED TEST_EXPECTED_OUTPUT_DIR)
|
|
message(FATAL_ERROR "Testing variable TEST_EXPECTED_OUTPUT_DIR is not set")
|
|
endif()
|
|
set(expect_arg "${TEST_EXPECTED_OUTPUT_DIR}/$<TARGET_BUNDLE_DIR_NAME:TestingAppBundle>")
|
|
if(NOT "${actual_arg}" STREQUAL "${expect_arg}")
|
|
message(FATAL_ERROR "xctest argument expected to be:\n"
|
|
" ${expect_arg}\n"
|
|
"but was:\n"
|
|
" ${actual_arg}\n"
|
|
)
|
|
endif()
|