• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Xcode 4 bug building iOS project that depends on Mac tools / looking for workaround
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Xcode 4 bug building iOS project that depends on Mac tools / looking for workaround


  • Subject: Re: Xcode 4 bug building iOS project that depends on Mac tools / looking for workaround
  • From: "Van Tol, Ladd" <email@hidden>
  • Date: Wed, 23 Mar 2011 23:07:27 -0600
  • Acceptlanguage: en-US
  • Thread-topic: Xcode 4 bug building iOS project that depends on Mac tools / looking for workaround

I think you can get around this by clearing the environment prior to running xcodebuild:

In your shell script phase, try something like this:

/usr/bin/env -i xcodebuild -configuration Debug

On Mar 23, 2011, at 3:43 PM, Eric Wing wrote:

I'll file bugs shortly, but I was hoping to get some ideas for workarounds.

I am trying to use Xcode 4. I have a complex iOS project that needs to
build Mac command line tools that will be executed as part of my iOS
build phases (via script phases).

The first problem I hit was when I did a cross-project dependency,
Xcode incorrectly built the command line tools with the wrong
parameters (ignored the settings in the tools' Xcode projects). For
example, my tools are setup for 32-bit Intel only, but when invoked
via a cross-dependency, it was trying to build as 64-bit Intel. If I
removed 64-bit as a valid architecture in the tools Xcode project, the
build would just fail. My tools are not 64-bit clean at the moment and
I don't really trust what Xcode is doing anyway so I devised a
workaround.

Instead of a cross-project dependency, I made a new script phase and
invoked xcodebuild directly on my projects. This worked until the
moment I tried to build for device instead of simulator. Now I am
getting failures with the message:

[BEROR]CodeSign error: code signing is required for product type
'Command-line Tool' in SDK 'Mac OS X 10.6'


So now I need a new workaround. If I manually break up everything into
manual separate build steps to build my tools separately, this seems
to work. But I really want a way to build in one-shot. Any help is
appreciated.

Thanks,
Eric
--
Beginning iPhone Games Development
http://playcontrol.net/iphonegamebook/
_______________________________________________
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

 _______________________________________________
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

  • Follow-Ups:
    • Re: Xcode 4 bug building iOS project that depends on Mac tools / looking for workaround
      • From: Eric Wing <email@hidden>
References: 
 >Xcode 4 bug building iOS project that depends on Mac tools / looking for workaround (From: Eric Wing <email@hidden>)

  • Prev by Date: Re: why isn't Xcode 4 even smarter?
  • Next by Date: Re: Why does XCode 4 always open files up to maximum size?
  • Previous by thread: Xcode 4 bug building iOS project that depends on Mac tools / looking for workaround
  • Next by thread: Re: Xcode 4 bug building iOS project that depends on Mac tools / looking for workaround
  • Index(es):
    • Date
    • Thread