Re: Questions about target build settings
Re: Questions about target build settings
- Subject: Re: Questions about target build settings
- From: Scott Tooker <email@hidden>
- Date: Mon, 26 Jan 2004 15:14:41 -0800
On Jan 19, 2004, at 2:29 AM, j o a r wrote:
> Hej,
>
> I'm trying to optimize the process of compiling prefix headers. While
> looking through our build settings I ended up with a couple of
> questions and feature requests:
>
>
> Question 1)
>
> Why is it not possible to find the Xcode documentation in HTML format
> on developer.apple.com? I don't like the integrated help viewer thingie
> found in Xcode - perhaps out of an aversion for custom
> HTML-help-document-viewers caused by exposure to Help Viewer.
I'd file a bug requesting this enhancement. It's not an unreasonable
request.
>
> Question 2)
>
>> Xcode provides a number of predefined collections, including a set of
>> commonly used settings.
>
> Does the "Common Settings" smart group have anything to do with the
> build settings for the inspected target, in the way that the "Custom
> Settings" smart group do? Which leads to;
the "Common Settings" collection contains all the build settings that
are considered to be "common settings" that most developers would
use/modify. That said, whether something is common or not can seem a
bit arbitrary and we are looking at how to make the collection clearer
(or just replace it with something else or remove it) in a future
version.
>
> Question 3)
>
>> The Customized Settings collection shows all of the build settings
>> that have been explicitly set in the target. This does not include
>> default settings provided by Xcode
>
> Is there any way to view all build settings that apply to a particular
> target? I would like to be able to have a graphical representation of
> what will eventually be passed to the compiler.
There is no "summary view" for build settings at this time (this
becomes more important when build styles are thrown into the mix). It's
something we want to add in a future release. Right now the only real
source of truth here is to look at the actual build log :(
>
>
> Feature request 1)
>
>> Build settings can be defined in other places in addition to a
>> targetfor example, you can define a build setting in a build style.
>> This flexibility lets you change build settings quickly without having
>> to create a new target.
>
> This implies that the build settings set in a build style should be
> ones that you would like to be able to toggle for the targets in your
> project. We use build styles like this, but we also use it to set
> default values for our targets, something it's not really suited to do
> as it overrides target settings, and as they apply to all targets.
>
> This has been requested in the past, but I would just like to chime in:
> It would be extremely useful to have "target groups" where you could
> set default build settings for a group of targets. You would then only
> have to set target specific build settings in the target itself. Our
> project have about 150 targets, it takes a lot of time to keep them
> "synchronized" as we:
>
> - Can't edit more than one target at a time, even for shared build
> settings
> - Have to set build settings individually on a per target basis.
While it doesn't fully address what you are asking for, in a future
version of xcode we want to add multiple selection for the inspectors
(or make it work more consistently) so you could select 5 targets and
apply the changes to all of them.
>
> In fact, it would be useful to also have "build style groups", because
> even though we only have four build styles in our project, we regularly
> (I could not claim that it was often, but it's still often enough...)
> have to change build style settings on up to four branches of the
> project = (16 individual build styles * (the number of build settings
> per style)).
>
> Feature request 2)
>
> Perhaps the ability to reference the target name in a target build
> setting could be introduced? That way we could specify that the target
> info.plist file name is "Info-(TARGET_NAME).plist", and that the target
> build product name is "(TARGET_NAME)".
File a bug for this. In general you can do this with
$BUILD_SETTING_NAME, but I don't think we expose the target name as a
build setting.
Scott
>
> j o a r
>
> [demime 0.98b removed an attachment of type
> application/pkcs7-signature which had a name of smime.p7s]
> _______________________________________________
> xcode-users mailing list | email@hidden
> Help/Unsubscribe/Archives:
> http://www.lists.apple.com/mailman/listinfo/xcode-users
> Do not post admin requests to the list. They will be ignored.
[demime 0.98b removed an attachment of type application/pkcs7-signature which had a name of smime.p7s]
_______________________________________________
xcode-users mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/xcode-users
Do not post admin requests to the list. They will be ignored.