Re: Aggregate Project and how to force targets to use a particular configuration
Re: Aggregate Project and how to force targets to use a particular configuration
- Subject: Re: Aggregate Project and how to force targets to use a particular configuration
- From: Scott Tooker <email@hidden>
- Date: Tue, 5 Sep 2006 09:42:48 -0700
In Xcode 2.4 if you build a target that references targets from other
projects (via cross-project references) then the build system will use
the active configuration name of the master project when choosing the
configuration to build in the sub-projects. This is why we tell users
to use the same set of configuration names across projects (if Xcode
can't find a matching configuration name, then it falls back to use
the default configuration name for that project).
It's important to note that the build settings defined in the
configuration used by the master target are NOT passed down to the sub-
targets.
Scott
On Sep 3, 2006, at 7:28 AM, Alfred Van Hoek wrote:
Perhaps documented. But I have a pure aggregate project to which
four xcode projects were added, 3 projects define static libs, and
the other defines the final product as a dylib. Working from the
aggregate works splendid, but how can I manage to change the
configuration of the targets in the sub projects (targets are ppc
and i386, currently set for deployment/release) to debug? The
aggregate does not have a configuration to begin with...
Alfred
_______________________________________________
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