Re: Radar issues (Re: How to file a radar)
Re: Radar issues (Re: How to file a radar)
- Subject: Re: Radar issues (Re: How to file a radar)
- From: Ben Weiss <email@hidden>
- Date: Wed, 19 Jul 2006 18:10:14 -0700
On Jul 19, 2006, at 6:00 PM, Dirk Stegemann wrote:
Hi,
Am 20.07.2006 um 03:41 schrieb Marshall Clow:
At 5:15 PM -0700 7/19/06, Chris Hanson wrote:
What do you mean by "separate debug/release libraries"?
Well, what _I_ mean is to have two static libraries - a debug and
a release version
and have the release version of my app link against the release
version of the library,
and the debug version link against the debug version.
Unless I'm missing something, you should be able to set your debug/
release target's library search path setting to the appropriate path.
This would require to
- have the same name for both libraries
- keep libraries in different directories
Or, why don't you just add the static debug lib to your debug
target, the static release lib to your release target? I'd guess,
Xcode should do the path adding stuff automagically, doesn't it?
The only way I've found to do it is to set linker flags directly in
the target settings (e.g. -lmylibrary in release and -lmylibrary_d in
debug), but then the app doesn't recognize when the static library
changes, so every time I make a change to the static library, I have
to manually touch something in the app that uses it and rebuild to
get it to link to the updated library. This is a major cause of
inadvertent version skew in my project. There was a thread a while
back about further ways to hack around this, but it really needs to
be (and should be) supported more directly in XCode.
Ben
_______________________________________________
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