search

asmallteapot / cocoapods-playgrounds

:black_joker: Generate Swift Playgrounds for any library.
MIT License
1.29k stars 42 forks source link

broken with CocoaPods 1.0.0 #22

Closed icanzilb closed 8 years ago

icanzilb commented 8 years ago

After upgrading to CP 1.0.0 the playground produced by the plugin can't find it's pods, like so:

pod playground RealmSwift ->

image

neonichu commented 8 years ago

:scream:

neonichu commented 8 years ago

This is caused by the scoping of product build directories done in CP 1.0, the RealmSwift.framework will be in a subdirectory which is not part of the frameworks search path of the Playground.

I think the best course of action is to add a copy or symlink step to the dummy target we're creating, so that pod install or pod update would still work within the generated project. Another approach would be copying the frameworks as part of pod playgrounds similar to the way it is done right now when using Carthage.

icanzilb commented 8 years ago

Carthage 😱

yurrriq commented 8 years ago

@neonichu, can you elaborate on the symlink solution? I'm not sure what to do, but would love to try out your tool.

neonichu commented 8 years ago

I just shipped a new release which fixes this: https://github.com/neonichu/ThisCouldBeUsButYouPlaying/releases/tag/v1.0.0

The implementation was actually much easier, I'm just setting CONFIGURATION_BUILD_DIR in a post_install hook so that it plays nice with Playgrounds.

icanzilb commented 8 years ago

I installed it 4 minutes ago, but thanks for pinging me 👍 I'm gonna try to find a bit of time tomorrow to look into playing with it, will let you know if all is okay, thanks again for fixing it!

yurrriq commented 8 years ago

Awesome. Thank you!

icanzilb commented 8 years ago

great work Boris, all is fine again