You can clone with
HTTPS or Subversion.
When a user defines multiple targets, it could be that they will end up using two distinct target libs in one project target. This means that the user will have to be able to combine two xcconfig files to one.
It might be a good idea to generate two files per target. One which defines the actual values, but with namespaced keys and the actual xcconfig file which just imports the other one and assigns the values to the actual keys. This will allow the user to create aggregate configs from multiple target configs easily.
USER_HEADER_SEARCH_PATHS-Pods = "Pods/AFNetworking"
USER_HEADER_SEARCH_PATHS = USER_HEADER_SEARCH_PATHS-Pods
USER_HEADER_SEARCH_PATHS-Pods-test = "Pods/Kiwi"
USER_HEADER_SEARCH_PATHS = USER_HEADER_SEARCH_PATHS-Pods-test
Say the user now wants to use both the Pods libs in one target, then they can easily combine the configs like so:
USER_HEADER_SEARCH_PATHS = $(USER_HEADER_SEARCH_PATHS-Pods) $(USER_HEADER_SEARCH_PATHS-Pods-test)
Closing this as apparently fixed in #79.
No #79 is about multiple projects in one workspace, this is about creating re-usable xcconfig files.
Somewhat related: #911.
Moving to #833