Target-specific library inclusion?
Target-specific library inclusion?
- Subject: Target-specific library inclusion?
- From: "Blair M. Burtan" <email@hidden>
- Date: Fri, 19 Sep 2008 08:37:58 -0700
Let's say you have two projects, one for a library and one for an
application that includes the library. I'd like to be able to build both
debug and release versions of the library (or GCC versus ICC or GCC 4 versus
GCC 4.2) with different names. Then in the application project I'd like to
have different targets but be able to automatically use a specific library.
Right now I have to uncheck one and check another in the project window to
do this. Is there some way to set up a rule or some other mechanism to do
this? Note that I do not want to use a single file name for the library. I
want to be able to tell the difference e.g. LibDebug.a, libRelease.a,
libGCC42.a, libICC.a.
This request could also cover the case where a third-party library is
released as two separate files for Intel and PPC but only one should be
included for the specific platform's link phase. Right now you get a
warning.
Blair M. Burtan
Northern Lights Productions
www.northernlights3D.com
_______________________________________________
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