How does SDK Root affect compiles?
How does SDK Root affect compiles?
- Subject: How does SDK Root affect compiles?
- From: Rick Mann <email@hidden>
- Date: Mon, 19 Feb 2007 19:50:58 -0800
I've noticed that if I provide an SDK Root, Xcode creates the
following link step for my app.
/usr/bin/gdc
-o /Users/rmann/Darbon/darbon/trunk/examples/Demo/xcode/build/
Debug/Demo.app/Contents/MacOS/Demo
-L/Users/rmann/Darbon/darbon/trunk/examples/Demo/xcode/build/Debug
-L/Users/rmann/Darbon/darbon/trunk/examples/Demo/xcode/../../../
target/lib
-L/Developer/SDKs/MacOSX10.4u.sdk/usr/lib/gcc/i686-apple-
darwin8/4.0.1
-L/Developer/SDKs/MacOSX10.4u.sdk/usr/lib/gcc/darwin/gdc.0.17
-F/Users/rmann/Darbon/darbon/trunk/examples/Demo/xcode/build/Debug
-filelist /Users/rmann/Darbon/darbon/trunk/examples/Demo/xcode/
build/Demo.build/Debug/Demo.build/Objects-normal/i386/Demo.LinkFileList
-arch i386 -Wl,-Y,1455
-mmacosx-version-min=10.4
-framework Carbon
-Wl,-syslibroot,/Developer/SDKs/MacOSX10.4u.sdk
If I don't provide the root, the line looks like this:
/usr/bin/gdc
-o /Users/rmann/Darbon/darbon/trunk/examples/Demo/xcode/build/
Debug/Demo.app/Contents/MacOS/Demo
-L/Users/rmann/Darbon/darbon/trunk/examples/Demo/xcode/build/Debug
-L/Users/rmann/Darbon/darbon/trunk/examples/Demo/xcode/../../../
target/lib
-L/usr/lib/gcc/i686-apple-darwin8/4.0.1
-F/Users/rmann/Darbon/darbon/trunk/examples/Demo/xcode/build/Debug
-filelist /Users/rmann/Darbon/darbon/trunk/examples/Demo/xcode/
build/Demo.build/Debug/Demo.build/Objects-normal/i386/Demo.LinkFileList
-arch i386 -Wl,-Y,1455
-framework Carbon
Notice that with the SDK root, it adds
-L/Developer/SDKs/MacOSX10.4u.sdk/usr/lib/gcc/darwin/gdc.0.17
(which doesn't actually exist, but that's beside the point).
I'm using a D-language plugin made by someone else, and I thought
that it must indicate somewhere to include that directory, but I
can't find anything in its files that matches. I want to adjust
things so it actually looks in the right place, but I don't know
where this stuff comes from.
The root cause of all this: if I link on the command line using
something like:
$(GDC) -framework Carbon -framework CoreFoundation -g -o $(APPTRGT)/
Contents/MacOS/$(EXNAME) $(OBJ) $(APIOBJ)
It links just fine. But the gdc call inside Xcode fails to include a
couple of libraries implicitly included by the gdc command line
(libgphobos, the std D library and libgcc_eh.a, exception handling
for gcc).
So, I'm trying to figure out how to get Xcode (or gdc when called by
Xcode) to "do the right thing" without having to explicitly include
the libraries in the project (they're not required for Carbon app
projects, for example).
TIA,
--
Rick
_______________________________________________
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