linking to libs that use a different build location is working now?
linking to libs that use a different build location is working now?
- Subject: linking to libs that use a different build location is working now?
- From: Rua Haszard Morris <email@hidden>
- Date: Wed, 26 Jul 2006 14:02:46 +1200
At this point it is generally nice to have a shared build
location so that all your build products end up in the same
place.
In fact this is not just nice but essential - Xcode will get the
dependencies wrong if the various products don't build in the same
place.
Originally I was of this opinion, but since Xcode 2.3 I've been
linking to library subprojects that use different build locations
without problems.
There was a "improved support for suprojects using diffferent build
locations" (or similar) release note which I took to mean this issue
was fixed.
Anyone have anecdotes to the contrary/caveats etc or is this actually
fixed now?
_______________________________________________
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