• 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: Can't get all targets to build in a Release configuration
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Can't get all targets to build in a Release configuration


  • Subject: Re: Can't get all targets to build in a Release configuration
  • From: Dan Korn <email@hidden>
  • Date: Thu, 4 Sep 2008 18:42:11 -0500

I've also experienced flakiness in building dependent targets when multiple configurations are involved.

AFAIK there's no way to make an "aggregate configuration" in Xcode. You can make an aggregate target which builds other targets, but you can't make a target or configuration which builds all the configurations (e.g. Debug and Release) of a target. Nor, again AFAIK, is there a way to specify more than one configuration with xcodebuild. And even if you have an aggregate target, dependencies can fail if all the configurations don't match up exactly.

Frankly, I don't really understand the benefit of multiple configurations. Ostensibly, they allow you to define a dependency once per target and have it apply to all configurations, so that, for example, you can make one project's target depend on another project's target in one shot, and it works for both Debug and Release configurations. The alternative is having to separately make your Debug target depend on the other project's Debug target and your Release target depend on the other project's Release target. However, in practice, I like to be able to explicitly build certain targets (not configurations) in dependent projects, without what I consider to be the double inconvenience of having to (a) set all my projects to build into the same place and (b) make sure that every target on every project has the exact same set of configurations with the exact same names, especially when some of these other dependent projects are from third parties or even simply managed by someone else with whom I can't always coordinate such changes.

This is just one of many reasons why I ignore configurations altogether in my projects and just make separate targets for Debug and Release. (Yes, like in CodeWarrior, although at least in Xcode you can set common settings at the project level.) Another reason is the inability to link to different Debug and Release builds of third-party libraries in a straightforward way without going into the low-level "Other Linker flags" setting or using xcconfig files. (IMNSHO one of the primary purposes/benefits of using an IDE like Xcode should be to avoid having to manage Unix-type build scripts.)

Dan

On Sep 2, 2008, at 5:15 PM, Nick Pilch wrote:

Hi. I am trying to do builds from the command line and executing "xcodebuilde -allTargets". However, I find that it skips an Aggregate target that I have. If I execute "xcodebuilde -allTargets - configuration Debug", the target is built. I couldn't find any documentaiton on this behavior. Any clues? Thanks.

_______________________________________________ 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: Can't get all targets to build in a Release configuration
      • From: "Robert Allen" <email@hidden>
References: 
 >Can't get all targets to build in a Release configuration (From: Nick Pilch <email@hidden>)

  • Prev by Date: Re: objc_exception_throw breakpoint not working
  • Next by Date: RE: Can't get all targets to build in a Release configuration
  • Previous by thread: Can't get all targets to build in a Release configuration
  • Next by thread: RE: Can't get all targets to build in a Release configuration
  • Index(es):
    • Date
    • Thread