Add support for integrating static library targets #842

Closed
paynechu opened this Issue Mar 10, 2013 · 6 comments

Comments

Projects
None yet
4 participants

I created a static library project with some dependencies managed by Cocoapods' Podfile. But what I dont want is the static library project to link with libPods.a. it should only use the header files. any way to do that?

Owner

fabiopelosin commented Mar 11, 2013

Did you try to running pod install --no-integrate? It will only make the Pods project without the workspace. Then you need to configure your target to use the xcconfigs generated by CocoaPods and you should be good to go.

thanks for your reply, but mostly not the case I dont want integrate fully, because I may have two targets in one project file, e.g. one is static one is executable, I just dont want the static library project to link with the libPods.a but still use the header files easily. if that can automatically finish by just pod install is great. actually just a little bit change can be done. only need to check if that project is static library project or not. if static library project just dont add the file reference to frameworks build phase. Because normally static library project dont want to embed dependencies to .a file they just need dependency libraries' header files for easy development.

fabiopelosin reopened this Mar 11, 2013

Owner

fabiopelosin commented Mar 11, 2013

This is somewhat related to #117.

walsh06 commented Jun 24, 2013

Im fairly sure this is the answer to the problem I have been having for the last few days. I was wondering what do I do to configure the target as you mention here : "Then you need to configure your target to use the xcconfigs generated by CocoaPods and you should be good to go."

Owner

alloy commented Jun 24, 2013

@walsh06 See step 6 here.

Owner

fabiopelosin commented Nov 11, 2013

Moving to #1250

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment