Re: Deployment phase failure
Re: Deployment phase failure
- Subject: Re: Deployment phase failure
- From: Scott Tooker <email@hidden>
- Date: Fri, 31 Oct 2008 17:02:38 -0700
On Oct 31, 2008, at 4:43 PM, Harry Plate wrote:
Scott,
Are you running xcodebuild as a different user? If so, you'll need to
define the source tree for that user too.
Nope. Same user...
and (as Chris points out) you are not running xcodebuild under sudo?
Scott
You might also check and see if you have a rogue com.apple.xcodebuild
prefs file hanging about. If you do, get rid of it and see if that
helps.
No such file found anywhere...
I modified my test script (that invokes 'xcodebuild') and added all
the
definitions that were available in my Xcode "Source Trees"
preferences. And,
voila, all my clean/build failures go away. So that confirms that
'xcodebuild' is not reading Xcode preferences (at least in my mind).
Perhaps this is by design? I am looking at getting these definitions
into my
shared .xcconfig files. Perhaps that is the right way to get around
this...
-harry
Scott
On Oct 31, 2008, at 2:31 PM, Harry Plate wrote:
Ok, I seem to have a variation of this theme happening to me, but it
centers
on 'xcodebuild'.
First of all, all the my Xcode projects (fm 2.5.1) compile just fine
on my
new Leopard system with Xcode 3.1.1
BUT, many of my cron (using xcodebuild) builds fail. And they fail
cuz of
the dreaded "Argument list too long: recursive header..." log entry.
So chkg the USER_HEADER_SEARCH_PATHS I found a couple of recursive
entries,
and I eliminated those, but my cron script would still fail (and my
Xcode
task would succeed).
Then I eliminated another recursive search (that came from
a .xcconfig file
that many of my projects share) that was defined like this:
$(ExternalSDK)/**
Where "ExternalSDK" was defined in the Xcode "Source Trees"
preferences.
So it appears that these settings do NOT work with 'xcodebuild' - I
say this
because it appears the "$(ExternalSDK)/**" resolves to "/**" which
is the
recursive header culprit. Certainly modifying the definition
(eliminating
the recursion) fixes the "Argument list too long: recursive
header..."
error; but, of course, the build phase fails cuz it cant find some
the
subdirs under the $(ExternalSDK) folder.
Is it true that the Xcode settings are no longer available to
'xcodebuild'
in 3.1.1 (workd just fine in 2.5.1). Or is some other magic is
required? I
suppose I could add the definitions to the script - but now I have 2
places
to deal with in event that my own "source trees" change.
-harry
Checking Dependencies
Argument list too long: recursive header expansion failed at /
Developer/Documentation/DocSets/
com.apple.ADC_Reference_Library.CoreReference.docset/Contents/
Resources/Documents/documentation/AppleScript/Conceptual/
AppleEvents/
dispatch_aes_aepg.
Can someone explain what this means ( XCode 3.1.1 ) ?
It means that for reasons we can't discern, you have added a
recursive search path in your Header Search Paths that is looking
in
your /Developer/Documentation folder. You shouldn't need any
Header
Search Paths to that location, and especially not a recursive one.
Chris
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
@apple.com
This email sent to email@hidden
_______________________________________________
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