-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
[SR-14245] Allow binaryTarget
s to declare dependencies
in the Swift packages
#4449
Comments
@swift-ci create |
Interested to see this implemented. The errors when a binary dependency is missing are very confusing. Wondering where to file an issue for better error messages. |
I'm actually running into this issue now, and it's fairly painful. Would really love to see a way to handle this better. |
Hi @tomerd, any news to schedule and process this enhancement request? Thanks. |
I added an evolution pitch to make this change: https://forums.swift.org/t/accepting-spm-binary-target-dependencies/60619 |
Additional Detail from JIRA
md5: ba6217da9eadde076a638765bd2e2d45
Issue Description:
Description
Currently the binary target feature in the Swift Package Manager only works for single binary dependencies. The API for `Target` is shaped so that its own static method for returning a `.binaryTarget` does not take a `dependencies` array like the standard `.target` method.
Setting the `dependencies` property on a `Target` type when that type is `binary` results in a crash to the SPM.
There is a workaround for the including dependencies in binary targets but it includes adding a dummy target to your `package.swift` and the result also generates warnings in an integrator's xcode project.
The desired change to the SPM is to allow `binaryTarget`s to declare `dependencies` in their `package.swift` files.
This thread has good detail on the issue and the known workaround for it: https://forums.swift.org/t/swiftpm-binary-target-with-sub-dependencies/40197/11
The text was updated successfully, but these errors were encountered: