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
Swift Sodium 0.9.1 with Swift Package Manager on ARM64/M1, Xcode 12.3, Big Sur 11.1 #231
Comments
Confirmed this occurs with empty project too.
I have looked at the copy files phase and can't see anything to change. |
Spent some time troubleshooting this, seems to be a Swift Package Manager issue. |
@jedisct1 - are you seeing this on your DTK? |
I've never noticed anything like that, but maybe I didn't look at the right place :) Does it prevent the application from compiling, launching or being packaged? |
@jedisct1 no, it compiles and works :) It's just a warning, it's weird though, even on a "hello world" type app, just importing via SPM and including an "import Sodium" - then this warning occurs. On both my M1 machines. |
@johnalanwoods try to |
@plananderson, archive works, but warning remains. |
🤔 |
Think this is a Swift-Sodium issue, not seeing it in any other projects using other libs. |
I get this warning multiple times on each build. Swift-Sodium 0.9.1, SPM, Intel based Mac, Xcode 12.4, macOS 11.2.3 |
Also happening on Catalina. |
@jedisct1 - no longer occurs in Big Sur 11.4 with Xcode Version 12.5 (12E262). Closing. |
I've been teaching the use of Swift Sodium with Cocoapods, now I'm using an M1 Mac and using the Swift Package Manager and latest version of SS, 0.9.1.
Whenever I use it to create command line apps in Big Sur 11.1, I noticed that although it creates a target (that also seems to work), I see the following warning:
Skipping duplicate build file in Copy Files build phase: /Users/john/Library/Developer/Xcode/DerivedData/myApp/SourcePackages/checkouts/swift-sodium/Clibsodium.xcframework/macos-arm64_x86_64/libsodium.a
Only seems to occur with SPM, any idea how to resolve?
The text was updated successfully, but these errors were encountered: