> I think what I suggested works well though. Add target references for all of a Pods dependencies to the Target Dependencies phase. This alone resolves the command line building. To address #731, just remove the library references from the Frameworks Build Phase and add the linker flags to a private xcconfig file for the integration library (libPods.a).

:+1:

> This does generate an aggregate static library, but through linking, not through lipo. So the result is a single libPods.a (and libPods-target-definition.a for other target definitions).

@alloy Did you mean to generate an additional single lib for the whole Pods project?

> 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?

Why is not going to be possible? Actually I think that his patch is a pre-requisite for this option of integration. Because with this patch is much easier to edit the Pod project in place (just recreate the targets of the changed pods).

> and it can't be solved with a target dependency because you can't add target dependencies across projects in a workspace.

Haven't tested it in the UI. But there is something interesting [here](https://github.com/CocoaPods/Xcodeproj/blob/master/lib/xcodeproj/project/object/reference_proxy.rb#L10).