Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I have a static library that depends on some of the Apple frameworks though when I include it as a target dependency I still need to add the frameworks it depends on to the application project. Is there some way to setup the project such that the dependencies only have to be specified in the static library target?
While I’m sure it is possible, you really don’t want to do that. I’m not sure you’d be able to get accepted if you did that. The static library is linking against dynamic library, the symbols are not included in it like the .m files are. That is the whole point of dynamic libraries.
One solution is to use an xcconfig file.
http://developer.apple.com/library/ios/#recipes/xcode_help-project_editor/Articles/BasingBuildConfigurationsonConfigurationFiles.html
In this scenario you create a sharable xcconfig file that accompanies the static library. Then in your application project you copy the xcconfig file and base your application configuration on it.