Re: Propagating build settings to sub-projects
Re: Propagating build settings to sub-projects
- Subject: Re: Propagating build settings to sub-projects
- From: Rick Mann <email@hidden>
- Date: Thu, 18 Nov 2010 14:45:20 -0800
On Nov 18, 2010, at 14:40:11, Christiaan Hofman wrote:
>
> On Nov 18, 2010, at 23:36, Rick Mann wrote:
>
>> Ah, OK. Oof, that really limits the usefulness of subprojects in a large org.
>>
>> However, it does seem that some settings are pushed down, right?
>>
>> --
>> Rick
>>
>
> I thought I said that: no. Only the "active" settings (like active build config) are propagated.
Well, I guess I'm not sure what you mean. Those "active" settings are all that I'm interested in propagating, and presumably include the key ones I'm interested in: SDKROOT, IPHONEOS_DEPLOYMENT_TARGET, TARGETED_DEVICE_FAMILY...
And of course, I'm interested in propagating the name of the active configuration (so that all the subprojects build/link against debug, release, etc).
>
> Christiaan
>
>> On Nov 18, 2010, at 14:22:07, Christiaan Hofman wrote:
>>
>>>
>>> On Nov 18, 2010, at 22:59, Rick Mann wrote:
>>>
>>>> Where do I look to see how to get my master Xcode project to tell sub-projects what OS target and deployment settings to use?
>>>>
>>>> We have sub-projects used in a number of other products. The products target different OS devices, versions, and minimum versions. We need the master project to dictate all that.
>>>>
>>>> Where is that discussed? What is the feature called (for better Googling)?
>>>>
>>>> TIA,
>>>> Rick
>>>
>>> AFAIK, this feature isn't called anything, because it does not exist. The docs (xcode build system guide) say how build settings are determined by all the project and target specific settings, and it does not mention anything like 'parent' projects. You can set some "active" settings (see the Project menu), which do propagate to cross-projects. But that's not really a project setting, rather a user build setting (they're not included in the docs, but I think they should be considered basically equivalent to the command line layer for xcodebuild, as they override all other settings).
>>>
>>> I think the only further thing you can do is to make the cross-project use config files from the 'parent' project. For instance, you could include the cross project in a subdirectory of the parent project, and have it use the config files in the parent directory. So depending on where the copy of the cross-project is located, it will use different settings. Of course this would make the projects themselves not stand-alone, and they would require the parent folder to contain these config files.
>>>
>>> Christiaan
>>>
>>
>
> _______________________________________________
> 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