Xcode should implement a portable way to locate xcconfig files in other projects

Originator:sam
Number:rdar://12096206 Date Originated:14-Aug-2012 06:21 PM
Status:Open Resolved:
Product:Developer Tools Product Version:
Classification: Reproducible:
 
14-Aug-2012 06:21 PM Sam Deane:
Workspaces are great, but if I have a project A that defines an xcconfig file that I want to use in project B, I have to either:

- drag the xcconfig file into project B
- add an xcconfig file to project B, and add an #include in it to the relative location of the file from project A

Both of these solutions impose the need to have a fixed relative location between project B and project A, which defeats one of the main advantages of workspaces.

This problem could be solved if the workspace implicitly collected together all of the xcconfig files from all projects in the workspace, and placed them in a known intermediate location, which was then implicitly in the search path for #include statements in xcconfig files.

Alternatively, if the build products location was implicitly in the #include search path for xcconfig files, it would be possible to include xcconfig files that had been built into that location by other projects.

Comments


Please note: Reports posted here will not necessarily be seen by Apple. All problems should be submitted at bugreport.apple.com before they are posted here. Please only post information for Radars that you have filed yourself, and please do not include Apple confidential information in your posts. Thank you!