Join GitHub today
GitHub is home to over 31 million developers working together to host and review code, manage projects, and build software together.Sign up
Add option to set “LINK FRAMEWORKS AUTOMATICALLY” to NO #48
The only way around this problem would be, according to people familiar with the matter, is to build the framework setting "Link Frameworks Automatically" set to no, which is currently impossible to do using Packager (amazing tool, I can't stress that enough).
I have set up sample repos that reproduce this issue for both a podspec called clever-framework and the Integrating app. In order to repo the issue,
Where did Metal come you ask? See,
This bug is in reality a bad Framework design for Apple and we can work around it only setting the "Link Frameworks Automatically" to NO so the linker doesn't bring more frameworks than it should to the binary.
Thanks for hearing me out
PS: I manually added the compiled
I see two options for supporting this in the packager:
Thinking about option 2, I am wondering if even CP should set this option in the
At least for the packager, I think it definitely makes sense to always set it to
For CocoaPods itself, it would right now make sense, but I have had this lingering thought that we could maybe use it one day to simplify our use of xcconfig files. Having said that, it’s definitely a maybe/sometime kinda situation, so for now I think it makes sense to completely disable it.