When a project is used through a FetchContent/add_subdirectory, the CMAKE_SOURCE_DIR path points to the calling project. This is resulting in some of the CI jobs attempting to FetchContent the macros from swift-corelibs-foundation/Sources/FoundationMacros, rather than swift-foundation/Sources/FoundationMacros, ultimately failing the build.
The project call sets a ${CMAKE_PROJECT_NAME}_SOURCE_DIR variable to the source directory of the project itself, making it more reliable. CMAKE_CURRENT_SOURCE_DIR would also work here too.
etcwilde
commented
2 months ago
When a project is used through a FetchContent/add_subdirectory, the
CMAKE_SOURCE_DIRpath points to the calling project. This is resulting in some of the CI jobs attempting to FetchContent the macros fromswift-corelibs-foundation/Sources/FoundationMacros, rather thanswift-foundation/Sources/FoundationMacros, ultimately failing the build.The
projectcall sets a${CMAKE_PROJECT_NAME}_SOURCE_DIRvariable to the source directory of the project itself, making it more reliable.CMAKE_CURRENT_SOURCE_DIRwould also work here too.Noticed in: https://ci.swift.org/view/all/job/swift-build-static-sdk/46