Re: Xcode - linking libraries based on Configuration
Re: Xcode - linking libraries based on Configuration
- Subject: Re: Xcode - linking libraries based on Configuration
- From: David Cohn <email@hidden>
- Date: Fri, 27 Jan 2006 07:59:35 -0800
Chris,
Things still aren't working...
One of the subprojects is called CTree.xcodeproj. So I add that to
my project.
It produces an output library called libCTree.a, so I check the box
to include that in my target.
Now I see libCTree.a in the target's "Link Binary With Libraries" phase.
But compiling gives me:
Libtool ... -lCTree
/usr/bin/libtool: can't locate file for: -lCTree
/usr/bin/libtool: file: -lCTree is not an object file (not allowed
in a library)
(& I see no reference to CTree's directory)
Thanks for your help,
--Dave
On Jan 26, 2006, at 10:09 PM, Chris Espinosa wrote:
On Jan 26, 2006, at 5:59 PM, David Cohn wrote:
I've got a project with two Build Configurations-- Debug and Release.
"Library Search Paths" includes a "Debug" directory for one
Configuration, and a "Release" directory for the other. (Both
directories contain a "linkedlib.a")
Don't do this.
But, I can't seem to specify linking to the actual library
("linkedlib.a") such that one Configuration finds the Debug
version, and the other finds the Release one...
What am I missing?
(This is still in Xcode 2.1...)
The best thing to do is if linkedlib.a is created by another Xcode
project, to a) add that subproject to your project, then b) select
linkedlib.a and in its inspector's Targets pane, check which
targets need to link to it. The configurations will be wired up
automatically.
Chris
_______________________________________________
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