Re: Xcode - linking libraries based on Configuration
Re: Xcode - linking libraries based on Configuration
- Subject: Re: Xcode - linking libraries based on Configuration
- From: email@hidden
- Date: Tue, 31 Jan 2006 11:34:48 -0500
I don't believe the search paths are
used or if they are used the filename does not get separated from the path
cleanly.
The only way I was able to use different
paths for different configurations was to add build steps
to copy the libraries around.
For example if project a links in a
static link from project b
I set up project b to copy the build
library from $CONFIGURATION/xxx.o to a common base folder.
Then I modified project a to copy from
the common base folder to $CONFIGURATION.
Lou Sakey
DFIS WW S+SE LOWELL DEVELOPMENT CTR
email@hidden
KNET 27-67676
978-323-7676
David Cohn <email@hidden>
Sent by: xcode-users-bounces+lou.sakey=email@hidden
01/31/2006 11:18 AM
|
To
| email@hidden
|
cc
|
|
Subject
| Re: Xcode - linking libraries based
on Configuration |
|
>> 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.
"Don't do this" seems unambiguously dire, but this is the only
way I
can get this to work...
Does anyone know why this shouldn't be done?
_______________________________________________
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
_______________________________________________
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