SDKROOT, -isysroot and -syslibroot
SDKROOT, -isysroot and -syslibroot
- Subject: SDKROOT, -isysroot and -syslibroot
- From: Gabriele de Simone <email@hidden>
- Date: Wed, 21 Dec 2005 10:15:21 -0500
Hi,
It is (or rather was) my understanding that setting the SDK build
setting to anything other than blank or root will cause the -isysroot
and -syslibroot flags to be passed to the compiler and linker.
I have since found out that -syslibroot is only passed to libtool
(never to ld) and only when creating static libraries. The unwanted
side effect of doing this is that if the static library links against
a dylib in a non-standard location /MyLibs/some.dylib (for example),
the linker will always fail to find the library even though the "/
MyLibs" path is added to the "Library Search Paths" build setting. It
seems that the linker is prepending the SDK path to all of the
"Library Search Paths", hence making it impossible to specify an SDK
*and* linking against dylibs in non-standard locations.
Is this really what's happening, and is there any way around it?
Thanks
Gabriele
_______________________________________________
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