build variants: please clarify
build variants: please clarify
- Subject: build variants: please clarify
- From: Andreas Grosam <email@hidden>
- Date: Wed, 10 Aug 2005 12:56:58 +0200
I didn't find much info about the build setting BUILD_VARIANTS and
how it is used in a project. A year ago there was a related question
in the xcode users mailing list, but no answer.
The doc mentions variants of "executables" - so what is meant with
"executable", is it also a shared lib, a static lib?
If I understand the documentation right, then there is a given set of
valid variants which can be "enabled" through including them in the
list? When the build setting string is empty, then the default is
"normal"
What exactly happens when I specify a certain valid build variant?
How does XCode know how to build the different variants?
Do I have any options to control this?
What happens when i specify an invalid variant?
How does XCode name the different "executables"?
Where does XCode place intermediate files of each variant, like .o
files?
Where are the "executable" placed in the different product types
(app, plugin, loadable bundle, shared lib, static lib, etc.)?
Can I control which variant to build in a certain build - or will all
variants be build unconditionally?
How can I specify the set of files, the build settings, and any other
option which might have an effect on a single build product for a
certain variant? (for instance when the set of files for the "normal"
variant differs from the "debug" variant)
How can I link to a certain variant of a product?
Are variant info passed thru from the parent project/target when
linking to a product in another project/target?
How can I execute/debug a certain variant of an application from
within Xcode?
Thanks
Andreas
_______________________________________________
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