Re: Xcode and Javadoc
Re: Xcode and Javadoc
- Subject: Re: Xcode and Javadoc
- From: Jeff Dunnett <email@hidden>
- Date: Fri, 20 Jul 2007 14:12:44 -0400
Date: Thu, 19 Jul 2007 17:15:24 -0700
From: Greg Guerin <email@hidden>
Subject: Re: Xcode and Javadoc
To: <email@hidden>
Message-ID: <l03130300c2c5ac7f2d82@[192.168.11.2]>
Content-Type: text/plain; charset="us-ascii"
Kyle Sluder wrote:
.profile is not processed by non-login shells.
Ermm... Right. I forgot about that.
That is something I missed. I had the CLASSPATH set right in
the .profile but forgot that it wasn't processed by non-login
shells. Thanks for point that out to me.
In fact, just like GNU Make, Xcode probably runs script phases in
a clean
environment, where no variables are set except for $SHELL.
No, Xcode explicitly sets a number of env-vars. Quite a number of
them.
Add this shell-script build phase, then look in the build transcript:
printenv | sort
Or just check the build transcript for the flurry of setenv's
The OP can add this line to his shell-script build phase, before the
'javacod' line:
printenv | grep CLASSPATH
and see if a CLASSPATH value is listed. If not, it would explain a
lot.
Explicitly set CLASSPATH at the top of the script and try again.
Or use the -classpath option of 'javadoc' itself.
Ultimately I used this option to set the classpath and the javadoc
worked perfectly once I had done that.
I must thank everyone here for the advice they've given me. It was a
great help.
Regards,
Jeff
_______________________________________________
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