Re: Problem with xcodebuild in Script
Re: Problem with xcodebuild in Script
- Subject: Re: Problem with xcodebuild in Script
- From: Philip Aker <email@hidden>
- Date: Tue, 21 Oct 2008 15:59:33 -0700
On Oct 21, 2008, at 2:25 PM, James Kelly wrote:
Hi all,
We're running Xcode 3.1.1 on 10.5.5. We've been noticing some strange
behavior in a project. We've been setting this up on a new build
machine,
and while it runs both in the GUI and and via xcodebuild on the
command
line, when run from a python script we have to do automated builds
(that has
built this project fine for a long time) the build fails, with this
error:
The actual error(s):
/Developer/SDKs/MacOSX10.4u.sdk/usr/include/StdArg.h:4:25: error:
stdarg.h:
No such file or directory
/Developer/SDKs/MacOSX10.4u.sdk/usr/include/float.h:8:24: error:
float.h: No
such file or directory
/Developer/SDKs/MacOSX10.4u.sdk/System/Library/Frameworks/
CoreServices.frame
work/Frameworks/CarbonCore.framework/Headers/MachineExceptions.h:
29:23:
error: xmmintrin.h: No such file or directory
/Developer/SDKs/MacOSX10.4u.sdk/System/Library/Frameworks/
CoreServices.frame
work/Frameworks/CarbonCore.framework/Headers/MachineExceptions.h:
254: error:
‘__m128’ does not name a type
/Developer/SDKs/MacOSX10.4u.sdk/System/Library/Frameworks/
CoreServices.frame
work/Frameworks/CarbonCore.framework/Headers/MachineExceptions.h:
255: error:
‘__m128i’ does not name a type
/Developer/SDKs/MacOSX10.4u.sdk/System/Library/Frameworks/
CoreServices.frame
work/Frameworks/CarbonCore.framework/Headers/MachineExceptions.h:
256: error:
‘__m128d’ does not name a type
** BUILD FAILED **
I've been looking at the environment variables as they exist when
run from
the script and when run from the command line, and I'm not seeing
anything
strikingly different, except that BASH was set to /bin/sh in the
python
script's environment while from the command line BASH is set to /bin/
bash.
I tried setting this to /bin/bash in python using os.environ before
initiating the build (via popen4) from python, but no dice.
I'll just confirm that we're issuing the command with *exactly* the
same
arguments in the python script as my test on the command line, and
we're in
the exact same directory. And this is something we've been doing
for a
while, on several different machines. This *is*, however, the first
time
we've attempted to do this with Xcode 3.1.1 (we've just updated the
project
file) so it's possible therein lies the problem.
Anyone have any ideas?
Thanks,
Jim
We just had a little "incident" where one developer was not using a
case-sensitive setup. For example StdArg.h != stdarg.h on such a system.
Philip Aker
echo email@hidden@nl | tr a-z@. p-za-o.@
Democracy: Two wolves and a sheep voting on lunch.
_______________________________________________
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