Skip to content

Conversation

@mhegazy
Copy link

@mhegazy mhegazy commented Jul 2, 2025

Since #10935 and #10937 landed, we are seeing failures while configuring llvm-project on Windows CI (see example failure). The root cause is unescaped path separators in LLVM_EXTERNAL_SWIFT_SOURCE_DIR, which leads to CMake configuration errors on Windows.

This PR addresses the issue by using cmake_path to normalize LLVM_EXTERNAL_SWIFT_SOURCE_DIR before it is appended to CMAKE_MODULE_PATH. This ensures the path is correctly formatted and portable across all supported hosts.

For context, LLVM_EXTERNAL_SWIFT_SOURCE_DIR is used in two places in llvm-project. The other use site leverages include_directories, which already handles path separators correctly on different hosts (see lldb/cmake/modules/LLDBConfig.cmake)

Testing:

  • Confirmed that the change resolves the Windows CI configuration failure.
  • No regressions observed on macOS or Linux builds.

Note: If landed, this change will need to be cherry-picked in next, and release/6.2

@mhegazy mhegazy requested a review from a team as a code owner July 2, 2025 23:44
@compnerd
Copy link
Member

compnerd commented Jul 2, 2025

@swift-ci please test

Copy link

@bulbazord bulbazord left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Makes sense to me.

@Steelskin
Copy link

@swift-ci please test windows platform

3 similar comments
@Steelskin
Copy link

@swift-ci please test windows platform

@Steelskin
Copy link

@swift-ci please test windows platform

@Steelskin
Copy link

@swift-ci please test windows platform

@Steelskin
Copy link

@swift-ci please test windows platform

@compnerd compnerd merged commit 0d0fb15 into swiftlang:stable/20240723 Jul 8, 2025
3 checks passed
@mhegazy mhegazy deleted the normalize-path branch July 8, 2025 21:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants