Re: How does SDK Root affect compiles?
Re: How does SDK Root affect compiles?
- Subject: Re: How does SDK Root affect compiles?
- From: Greg Guerin <email@hidden>
- Date: Tue, 20 Feb 2007 10:26:58 -0700
Chris Espinosa wrote:
>Xcode has only a monolithic notion of SDKs. If an SDK is set, every path
>into /System, /Library, and /usr gets the SDKROOT prepended. You either
>have to copy the gdc pieces into a copy of the 10.4u SDK and point the
>SDKROOT to that, or move the gdc pieces out of /usr and supply custom
>paths to them that won't be modified.
Two other possibilities, correct me if I'm wrong (I have not tried these).
1) Add a symlink to /usr/lib/gcc/darwin/gdc.0.17 in the 10.4u.sdk.
2) Create a whole new SDK directory containing symlinks:
cd /Developer/SDKs/
mkdir My10.4u+D.sdk
ln -s MacOSX10.4u.sdk/Developer My10.4u+D.sdk/Developer
ln -s MacOSX10.4u.sdk/System My10.4u+D.sdk/System
ln -s MacOSX10.4u.sdk/usr My10.4u+D.sdk/usr
cp MacOSX10.4u.sdk/SDKSettings.plist My10.4u+D.sdk
open -b com.apple.PropertyListEditor My10.4u+D.sdk/SDKSettings.plist
Then edit and save the plist as appropriate.
The symlink to the SDK's usr would probably have to be a partial copy
rather than a symlink, because you'd want to go into it and add a symlink
to /usr/lib/gcc/darwin/gdc.0.17 without affecting the original 10.4u SDK.
That is, the directory structure would be copied, so the dirs could be
modified without affecting the original 10.4u SDK, but the leaf files would
all be symlinks.
One reason this might not work is if Xcode would sometimes treat symlinks
differently than it treats real files or dirs. But if it's just evaluating
paths, I don't see why it wouldn't work. All the usual disclaimers apply.
-- GG
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden