Skip to content

Conversation

etcwilde
Copy link
Member

There is a bug in CMake CMP0157 where if library A depends on a non-Swift library B, which in turns depends on a Swift library C, library A will depend on a swiftmodule for B. B doesn't have a swiftmodule, so the build fails.

Currently hitting the following error on Windows CI:
ninja: error: 'swift/CCryptoBoringSSL.swiftmodule', needed by 'lib/libCCryptoBoringSSLShims.lib', missing and no known rule to make it

Disabling CMP0157 for now.

There is a bug in CMake CMP0157 where if library A depends on a
non-Swift library B, which in turns depends on a Swift library C,
library A will depend on a swiftmodule for B. B doesn't have a
swiftmodule, so the build fails.

Disable CMP0157 for now.
@Steelskin
Copy link
Contributor

Steelskin commented Jul 23, 2025

Non-owner LGTM. I just hit the same issue. This seemed to work with more recent CMake versions.

@Lukasa Lukasa added the 🔨 semver/patch No public API change. label Jul 23, 2025
@Lukasa Lukasa merged commit d79c573 into apple:3.12.x Jul 23, 2025
29 of 30 checks passed
Steelskin added a commit to Steelskin/swift that referenced this pull request Jul 23, 2025
Steelskin added a commit to Steelskin/swift that referenced this pull request Jul 23, 2025
Steelskin added a commit to Steelskin/swift that referenced this pull request Jul 23, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🔨 semver/patch No public API change.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants