From @AliSoftware comment in #125 .
This would allow to:
This should be done for each Pod - target combination as there might be differences (a common example is iOS and OS X builds).
Is anyone currently working on this issue? I am asking because I have put together a solution that works for my use cases, but I am very new to the project and I wanted to confer.
This solution works with multiple project targets and subspecs. I haven't looked into build configurations yet.
My need for this solution is similar to the prefix header contamination, but due to header or source conflicts when two different projects have the same header name. For example, two 3rd party libraries might both have a config.h.
My solution creates a static library target for every combination of library dependency / user target pair and ensures that each library is built in a 'sandbox' by not allowing project level includes (USE_HEADERMAP = NO). I will put up my work to date shortly, but I haven't fixed up any of the tests. I'm not sure if what I have put together even fits with the developers plans.
Awesome. To my knowledge there hasn't been anybody working on this. So please make a pull request (even without the tests) so we can inspect your patch. If you are interested in polishing it to get it merged I can help!
Add per-spec static library targets
Static library targets are created for each combination of user-target
and spec dependency. This addresses issue #841, although likely not