Re: Different library per build configuration?
Re: Different library per build configuration?
- Subject: Re: Different library per build configuration?
- From: Rippit the Ogg Frog <email@hidden>
- Date: Tue, 22 Sep 2009 19:59:17 -0700
It Worked! Just like you said. Thank you very much.
I was able to verify that the right library config was getting build
because the Release build had twice as many sources to compile as the
Debug build, being a 32-bit Universal.
Ken Thomases wrote:
* First, remove all references to libzoo.a from your application project
* Now, add the ZooLib framework project as a cross-project reference in
your application project
* Get Info on your application target and add a Direct Dependency,
choose the ZooLib static library target from the ZooLib cross-project
reference
* Toggle open the cross-project reference in the file list
* Drag the libzoo.a static library "virtual product" from there to your
application target's link build phase
With that set up, your app should link against the static library that
corresponds to the configuration you're building. When you build the
Debug configuration of your app, it will link against the library from
the Debug configuration of ZooLib -- it will build that library, if
necessary. Likewise, the Release build of your app will be linked
against the Release build of libzoo.a.
--
Rippit the Ogg Frog
email@hidden
http://www.oggfrog.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