Re: Buildstyles Propogating to sub projects in XCode 1.5 ?
Re: Buildstyles Propogating to sub projects in XCode 1.5 ?
- Subject: Re: Buildstyles Propogating to sub projects in XCode 1.5 ?
- From: Bryan Pietrzak <email@hidden>
- Date: Wed, 27 Apr 2005 11:16:12 -0500
On Apr 27, 2005, at 10:55 AM, Dave Camp wrote:
But they don't, not really. Build Styles don't let you bring in debug
libraries, or include/exclude source files that are only appropriate
for debugging of profiling, etc.
Half correct. You can change what libraries are used by changing the
linker flags using build styles.
Hmm, what if I have a vendor supplied library: "libSuperCool.a" and
"libDebugSuperCool.a". Last time I wrestled with build styles I
couldn't have the deployment style use one library and the debug style
use the other. But that was a while ago.
You can't change what sources are used.
If your debug source files were wrapped with appropriate ifdefs, you
could control the inclusion of the source by changing the Preprocessor
Macros setting. It's not the exact feature you are asking for, but in
some cases it's enough.
Sure there are workarounds, there's always are :) But they tend to be
cumbersome and not really best practices. An IDE is supposed to make
most things easy and the hard-to-impossible things possible. Xcode
tends to mix that up sometimes.
In my opinion, Build Styles are the right idea, just the wrong design.
They simply don't always solve the problem they're supposed to solve.
Where I come from that's a design problem.
Bryan
_______________________________________________
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