Re: static lib gets wrong path
Re: static lib gets wrong path
- Subject: Re: static lib gets wrong path
- From: Scott Tooker <email@hidden>
- Date: Thu, 24 Nov 2005 12:56:23 -0800
This is a well known limitation of Xcode. You need to have the
various projects share the same build products directory.
Your other option is to adjust the "Library Search Paths" of the main
project to include the build products directory of the subproject,
but that is only a partial workaround and will not work properly when
dealing with sub-projects that use dynamic libraries (due to how
Xcode uses DYLD_FRAMEWORK_PATH to reference built products when
running).
Scott
On Nov 24, 2005, at 3:21 AM, Stefan Werner wrote:
Hi,
I'm still not quite understanding how Xcode handles paths to
subprojects:
I created a new static library project that works just fine by
itself. Then I added that as a subproject to my main project and
checked the little checkmark next to the .a file to make my main
project link against it - just as I did with all the subprojects I
added previously. However, Xcode now insists on looking for my new
library in the build directory of the main project instead of the
subproject, whereas it finds all the other libraries in their
respective build directories. I can't find anything I did
differently with this library than all the others - is it because I
am using Xcode 2.2 now? Is there a way to make Xcode deal properly
with subprojects without having to use shared build directories?
Thanks,
Stefan
_______________________________________________
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