Re: Can't tell build configurations to use different libraries
Re: Can't tell build configurations to use different libraries
- Subject: Re: Can't tell build configurations to use different libraries
- From: Dave Thorup <email@hidden>
- Date: Thu, 18 Aug 2005 12:58:01 -0400
On Aug 18, 2005, at 11:37 AM, Rush Manbert wrote:
I believe you can do this by putting the debug and release library
versions in different directories, then specifying different
library load paths for each configuration. Of course, installing
the libraries in different places is another headache to deal
with... :-)
Except that this doesn't work when your Release and Debug libraries
are named differently (ex: foo.dylib & foo_debug.dylib). We've run
into this problem as well and I haven't been able to find a good
solution for it. Right now what I do is for any project that needs
to link with our libraries I create separate targets for each build
and a single build configuration. That way when I need to create a
Debug build I change to the Debug target and I never need to change
the build configuration (because there's only one).
Of course when you do it this way you run into the other problems
that you described when you need to manage multiple targets. I'd
really like for Apple to address this problem, it's really the only
major shortcoming that I have with the build configurations.
_____________________________
Dave Thorup
Software Engineer
email@hidden
http://www.kuwan.net
Defaults Manager - The premier editor for Mac OS X's User Defaults /
Preferences database.
_______________________________________________
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