Re: Per-configuration target membership and expectations
Re: Per-configuration target membership and expectations
- Subject: Re: Per-configuration target membership and expectations
- From: Chris Espinosa <email@hidden>
- Date: Wed, 19 Jul 2006 21:51:19 -0700
Before you all spin this debate still way farther than it needs to
go, I just want to let you know that we are well aware of the request
and the need.
Xcode is designed so that things work best when your project and its
dependencies a) are all Xcode projects, b) all use the same
configurations, and c) all share the same build directory. Then
building and linking to separate Debug and Release versions of a
library generated by a dependent project is more or less automatic.
But if you deviate from that, it gets much more difficult, though
it's far from impossible. In general Xcode requires the same set of
dependent files for all configurations in a target, and while it can
automatically pick per-configuration variants by location, it doesn't
do as well with, say, arbitrary names and locations for link
libraries per configuration. By fiddling with search paths and Other
Linker Flags and stuff you can manage it, but it's not as
straightforward as you -- or we -- want it to be.
And changing the fundamental architecture of the Xcode project and
build model is something that doesn't change quickly or without
cost. Please remember that when you bring your expectations to the
conference in three weeks.
Chris
_______________________________________________
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