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 16:18:32 -0500
On Apr 27, 2005, at 2:29 PM, Mike Pinkerton wrote:
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.
The way we got around this was to have the build style set a variable
with the library name (or path in our case) and then reference that in
the "other linker flags" build setting. Of course this only works with
things you can use with "-lFoopy" but it's better than two separate
targets with duplicate files for just one change.
Yeah, but I want to do this in a natural way. :)
I'd like to add both libraries to the target. Then, with the Deployment
build active, check a "box" to mark the debug build "inactive". And
vice-versa for the Development build.
The user interface for this "box" to check should be easily
discoverable :)
Inactive files in a target (based on build style) should have greyed
out names.
That would seem really easy compared to all these other approaches.
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