Skip to content
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

Workspace not integrating with Cocoapods #144

Closed
markflowers opened this issue Apr 24, 2014 · 9 comments
Closed

Workspace not integrating with Cocoapods #144

markflowers opened this issue Apr 24, 2014 · 9 comments

Comments

@markflowers
Copy link

Setting up a project with Liftoff, the project is missing all of the integration with CocoaPods. I attached a screenshot of the Build Phase showing that libPods.a isn't included in the project, not any of the other integration.

buildphase

I feel like maybe I'm just missing something, but I did a pod install separately and it still didn't update the project file correctly.

@gfontenot
Copy link
Member

Are you overriding the default Podfile? By default, we only include pods in the testing bundle, so nothing would be included in the app target.

@markflowers
Copy link
Author

Yeah, my idea was to go ahead and include a couple pods that we use on pretty much all of our projects.

That's not really an issue for me though since we can just manually do that after the project sets up. But more of the issue is that the project file doesn't even update if I modify the Podfile after Liftoff is done running.

@gfontenot
Copy link
Member

Can you paste your Podfile? Are the default pods included in the test target?

@markflowers
Copy link
Author

Nevermind, disregard the moron in the corner.

I didn't pay attention to the target in the Podfile. Sorry about that.

I've been working on creating custom project templates with Xcode and it is truly terrible. Thanks for all the work you've put into this already.

@gfontenot
Copy link
Member

Ok, cool. Is there anything that I could have done with regards to documentation that would have made this clearer?

@markflowers
Copy link
Author

I'm not sure if it really would need to be documented better. Maybe including an empty target for the actual project in the Podfile would help it be more self documenting and obvious. Probably not necessary, but it would have saved me on this I think.

@gfontenot
Copy link
Member

Typically we don't create a group for the app target, and instead leave project-wide pods at the base level. Maybe a comment in the default Podfile that says # Add Application pods here would help?

@markflowers
Copy link
Author

Oh yeah, you'd need the pods for testing as well possibly ...

Just having a comment would be good enough to make it obvious I think.

@gfontenot
Copy link
Member

Cool, I'll add that now. Thanks for the feedback!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants