Re: Giving up on build styles
Re: Giving up on build styles
- Subject: Re: Giving up on build styles
- From: Bryan Pietrzak <email@hidden>
- Date: Tue, 26 Apr 2005 14:57:28 -0500
On Apr 19, 2005, at 8:48 AM, Andreas Grosam wrote:
"build styles" are not appropriate for defining the
functionality/imports/exports of a product!
A product may have several *versions* (a debug or a release or
arbitrarily more) which may differ in their functionality and in
exporting/importing interfaces/libraries. This also may require a
different set of source files and resources, and a different set of
frameworks to link against.
For instance, the debug version of an application may include a "debug
menu". And the debug version of a certain framework may include source
files for checking the heap, showing the stack backtrace or provide
for certain other debugging functions. In the release version the
special debug functions shall not be available.
These "versions" are a completely different concept than that of
"build styles"!
Notice, each "version" may be compiled as deployment style, debug
style or whatever to build the product.
In XCode, you need to use different targets, when you have different
set of resources and files, or libraries to link against.
Sorry, but then your and Xcode's definition of build styles makes no
sense.
Having to use multiple targets is just a recipe for disaster -- making
sure new files get added to all the right targets, etc.
I have to pretty much completely agree with David's original
statements: build styles as they exist in Xcode 1.5 seem severely
hampered and Tim's workarounds involving shell scripts seem like a
complicated partial solution.
Seems to me that the while Build Styles may "work as designed", the
design itself is flawed.
Bryan
_______________________________________________
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