-
Notifications
You must be signed in to change notification settings - Fork 1.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Compilation Error: `Unable to resolve build file: ...' in Swift Packages during Universal Build #7442
Comments
This looks like a duplicate of #7405. Is this issue reproducible for you with latest development snapshots ( |
Although it appears to be very similar, this issue is still a separate new problem. I tested it with the latest swift-6.0-DEVELOPMENT-SNAPSHOT-2024-04-15-a, and I can still reproduce the issue in the demo I provided. |
I apologize, I accidentally closed this issue. It can still be reproduced in |
Is it reproducible with SwiftPM command-line tools:
swift build
,swift test
,swift package
etc?Description
A compilation error occurs when package access level modifiers are used in a dependent Swift Package while simultaneously building arm64 and x86_64 architectures.
Specifically, swift build, swift build --arch arm64, and swift build --arch x86_64 commands successfully compile individually without any errors. However, the command swift build --arch arm64 --arch x86_64 gives an error.
Consider the error message:
Expected behavior
Build succeeded and generated a universal binary.
Actual behavior
Build cancelled
Steps to reproduce
Download Foo.zip, then unzip it and change your current directory (cd) into the Foo directory.
Run the command swift build --arch arm64 --arch x86_64.
Swift Package Manager version/commit hash
5.10
Swift & OS version (output of
swift --version ; uname -a
)swift-driver version: 1.90.11.1 Apple Swift version 5.10 (swiftlang-5.10.0.13 clang-1500.3.9.4)
Target: arm64-apple-macosx14.0
Darwin Foo 23.5.0 Darwin Kernel Version 23.5.0: Tue Mar 26 20:55:54 PDT 2024; root:xnu-10063.120.88.501.3~2/RELEASE_ARM64_T6030 arm64
The text was updated successfully, but these errors were encountered: