Re: Pass a C option based on command-line output?
Re: Pass a C option based on command-line output?
- Subject: Re: Pass a C option based on command-line output?
- From: Daniel Jalkut <email@hidden>
- Date: Sat, 7 Jan 2006 17:46:53 -0500
On Jan 7, 2006, at 4:34 PM, Chris Espinosa wrote: Invoking random shell commands at any given step in an Xcode compilation would introduce unbounded complexity, and things are bad enough as it is. Besides, you really don't need to backtick-execute a shell command to get the host name, it's already set in the shell's $HOSTNAME variable.
Yeah - but executing random shell scripts in a build phase also introduces unbounded complexity, right? I don't know if you're gonna get away from that problem in a highly customizable IDE :) So in Preprocessor Definitions just set HOSTNAME=$HOSTNAME and be done with it.
On my machine it looks like I have $HOST. But in any case I don't have any luck trying to set a build setting with the expanded value. I've tried:
HOSTNAME=$HOST HOSTNAME=$(HOST) HOSTNAME=${HOST}
(This is on the Preprocessor Macros build setting)
Is there a particular build setting where I can "promote" shell variables into Xcode variables? Or is there a different format I'm supposed to use to expand them in a build setting's definition?
Thanks!
Daniel |
_______________________________________________
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