See:
video to see what I'm talking about. At the end, the guy making the video had to add the Search Path. I'd be interested in knowing why that is.
As I commented on the SciTech mailing list, this is the wrong way to go about this. The short answer to the latter question is "No" but there are ways you can work around it. There is one SDK root and it needs to have the set union of all the vendor SDKs you wish to use, including Apple's base SDK.
I think I would rather add the Search Path in the preferences than muck with the SDKs for Xcode! I think.
If you add paths from multiple SDKs (where I'm considering the root OS install as an SDK, the "Current Mac OS" one) you're just asking for trouble. There may be duplicate frameworks and libraries in those SDKs. Which one is the build chain supposed to magically know to pick?
As was stated, either don't use the /Developer/SDKs/, or put your 3rd party frameworks into them. Duplicate an existing one and modify that, if you're worried about it. You can use custom SDKs in Xcode - just select "Other" in the SDK menu, and click the "Choose" button to pick one, anywhere on disk.
Wade |
