RE: Can't get all targets to build in a Release configuration
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: "Robert Allen" <email@hidden>
- Date: Thu, 4 Sep 2008 20:17:42 -0700
- Thread-topic: Can't get all targets to build in a Release configuration
Using different targets for Release and Debug sounds like the workaround
I've been looking for since, as you say Dan, Xcode does not support
dependencies based on configuration as the more advanced IDEs do. Before
now I had resorted to the lower level flags.
Thanks,
-Robert
------------------------------------------------------------------------
--
"We are like dwarfs sitting on the shoulders of giants; hence we can
see more and further than they, yet not by reason of the keenness
of our vision, but because we have been raised aloft and are being
carried by men of huge stature." -- Bernard of Chartres, 1115
------------------------------
> -----Original Message-----
> From: xcode-users-bounces+rallen=email@hidden
> [mailto:xcode-users-bounces+rallen=email@hidden]
> On Behalf Of Dan Korn
> Sent: Thursday, September 04, 2008 7:42 PM
> To: Xcode Users
> Subject: Re: Can't get all targets to build in a Release configuration
>
> 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
>
_______________________________________________
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