I would guess because most people normally expect/want their dependent
projects all built the same way.
Conceptually, yes, but in practice, my library projects require
different style settings than my application project does.
Further investigation (which admittedly I should have done before
mailing the list) turned up the fact that the xcodebuild command-line
tool applies *no* build style to subprojects. That's a little better, I
think.
As a workaround for this issue, I tried a shell script build phase
instead of using dependencies, but it was slower and the way it comes
out in the Build Results window isn't as nice to work with. In any
case, when I'm using the XCode app, I shouldn't have to use the command
line tool for anything. That's the point of having a GUI app. (Unless I
need to get really fancy, but I don't think this qualifies.)
My impression is not that someone thought this was a good idea, but
that they didn't have time (or it wasn't a high priority) to implement
a better solution.
Perhaps you should have three choices (as a project setting) for
choosing build styles for subprojects:
- Use the subproject's own style with a matching name, if any,
otherwise none.
- Use the master project's style.
- Use no style.
That's the best relatively simple solution I can think of.
I'd suggest logging a feature request for a per-project setting that
disables this behavior for users like yourself. I can see how that
would be useful in some circumstances.
_______________________________________________
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
