Re: Development and Deployment linking to libraries
Re: Development and Deployment linking to libraries
- Subject: Re: Development and Deployment linking to libraries
- From: Bengt Nilsson <email@hidden>
- Date: Wed, 3 Sep 2008 17:22:07 +0200
- Auth-sender: email@hidden
3 sep 2008 kl. 17.05 skrev <email@hidden> <email@hidden
>:
Nick Zitzmann wrote:
On Sep 3, 2008, at 5:24 AM, Bengt Nilsson wrote:
I want to link my project to libproj/build/Development/mylib and
libproj/build/Deployment/mylib.
The libs are debug and release versions.
How do I make the distinction when I introduce the libs into my
project?
[...] Second, instead of linking the library to the project
directly, add
the library's project into the application's project (you can do this
by dragging the library's project bundle from the Finder into the
application project). Then, as long as you keep the configuration
names the same between the projects, Xcode will link the application
to the library in the corresponding build configuration.
Of course, but what if your library is already built in Debug/
Release flavors, and you don't have the source code (for example, a
third-party library)?
I got the advice to skip the dragging altogether and use "Other Linker
flags" and "Library search paths" in the Build settings and make the
distinction there:
Example:
Linker Flags: -liconv -lz -lwx_mac_static
Lib search paths: $(WXWIN)/src/build/Deployment or $(WXWIN)/src/build/
Development
I tried it and it works perfectly. The only "flaw" is that it is not
visible in the project GUI, but I can live with that.
Philippe
_______________________________________________
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