Re: C_INCLUDE_PATH & NEXT_ROOT -> Solution ?
Re: C_INCLUDE_PATH & NEXT_ROOT -> Solution ?
- Subject: Re: C_INCLUDE_PATH & NEXT_ROOT -> Solution ?
- From: Markus Hitter <email@hidden>
- Date: Thu, 14 Jul 2005 18:58:44 +0200
Am 14.07.2005 um 17:15 schrieb D. Walsh:
export NEXT_ROOT=/Developer/SDKs/MacOSX10.3.9.sdk C_INCLUDE_PATH=/
Developer/SDKs/MacOSX10.3.9.sdk/usr/include ./configure ...
You can either export an variable _or_ set a variable for one
invocation only.
# Note: first export variables, then issue configure
export NEXT_ROOT=...
export C_INCLUDE_PATH=...
./configure ...
or (no "export")
# Note: set some variables for the invocation of configure only
NEXT_ROOT=... C_INCLUDE_PATH= ... ./configure ...
I've seen the latter to fail sometimes, however. Obviously, configure
relies on variables to be exported (it forks subcommands without
taking care of those variables).
N.B.: Xcode 2.1 seems to move away from the NEXT_ROOT-type variables
and use the -syslibroot parameter instead:
export CC="gcc -syslibroot /Developer/SDKs/MacOSX10.3.9.sdk"
./configure ...
HTH,
Markus
- - - - - - - - - - - - - - - - - - -
Dipl. Ing. Markus Hitter
http://www.jump-ing.de/
_______________________________________________
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