El 09/08/2006, a las 10:40, Dirk Stegemann escribió:
If I understand correctly, because there are only aggregate
"targets" which refer to other targets, I'd currently have to either
1) restructure my project in a way that my target's configurations
"A_T1_C1..C3" become targets on their own ("A_T3..T5") which
feature just one configuration, so I can refer to them by an
aggregate target "A_T6",
If I understand your question correctly, then yes, I think that's
what you have to do.
Is there a better way to accomplish what I'm trying to do,
preferably without restructuring my current project and without
creating an "aggregate project"?
I definitely wouldn't split things off into a separate project.
Is there a special way to create aggregate targets which are able
to map to specific configurations inside the same project?
Configurations are project-wide, so it is only appropriate to include
settings that will apply to all sub-targets in an aggregate target at
once. If you need specific settings for a sub-target they'll need to
go in the build settings for that target.
You can minimize repetition by using xcconfig files at both the
project (configuration) level and the target level. One config file
can include another (and so on) so you can effectively build an
inheritance hierarchy of build settings. If you need even more
control I believe you can provide further overrides at the command-
line switch/environment variable level.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/xcode-users/email@hidden
