Link against SwiftJavaStatic instead of SwiftJava#42
Open
colemancda wants to merge 1 commit into
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
swift-java's own
Package.swiftdeclares itsSwiftJavaproduct astype: .dynamic, with a target (SwiftJavaRuntimeSupport) that statically depends on that same product's other target (SwiftJava). SwiftPM rejects this graph whenever any other dynamic library product also exists in the resolution — which happens for any app embedding AndroidKit into its own single.so(e.g. via a JNI bridge).SwiftJavaStaticis the product swift-java itself documents as the correct choice for static-linking consumers.Test plan
aarch64-unknown-linux-androidwith this change; the duplicate-linkage error is gone.