We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Any framework (say F) that depends on https://github.com/mattgallagher/CwlUtils.git will use a dynamic link library if the CwlUtils is consumed as a swift package.
This creates a problem because when another application A consumed the framework F it doesn't get a copy of CwlUtils.
The workaround listed in the readme creates missing CwlFrameAddress issues in application A.
The solution is again to consume CwlUtils in application A. Looks like the SPM doesn't know how to deal the dynamic libraries.
I believe the line is here: .library(name: "CwlUtils", type: .dynamic, targets: ["CwlUtils"]),
Does CwlUtils need to be dynamic?
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Any framework (say F) that depends on https://github.com/mattgallagher/CwlUtils.git will use a dynamic link library if the CwlUtils is consumed as a swift package.
This creates a problem because when another application A consumed the framework F it doesn't get a copy of CwlUtils.
The workaround listed in the readme creates missing CwlFrameAddress issues in application A.
The solution is again to consume CwlUtils in application A. Looks like the SPM doesn't know how to deal the dynamic libraries.
I believe the line is here:
.library(name: "CwlUtils", type: .dynamic, targets: ["CwlUtils"]),
Does CwlUtils need to be dynamic?
The text was updated successfully, but these errors were encountered: