static lib gets wrong path
static lib gets wrong path
- Subject: static lib gets wrong path
- From: Stefan Werner <email@hidden>
- Date: Thu, 24 Nov 2005 12:21:47 +0100
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