@irrationalfab I agree with your point regarding moving it into the xcconfig for #731.

@jasl8r Regarding df7a027, did you see my messages in Campfire from just before you joined?

In any case, where possible, we should be able to generate something that will build all the dependencies in isolation. I.e. without having to integrate it into a user project. We use this often to test a Podfile that a user pastes into a issue ticket or for a project like RubyMotion which only wants the resulting static library. I guess that means that CocoaPods should always generate a workspace, regardless of the use of `--no-integrate`.

Another potential issue is that currently people can integrate Pods.xcodeproj manually as a subproject, but I guess that's not going to be possible anymore?

Finally, just out of curiousity and because I haven’t checked that out yet, will the Pods.xcodeproj have aggregate targets that generate one static library by lipo-ing all the dependency libs together?