On Nov 30, 2005, at 3:52 AM, James Larcombe wrote:
Scott Tooker wrote:
For now, if you are using cross-project refererences, all projects
involved
need to build into the same location. We want to remove this
restriction
in a future version of Xcode.
This seems to be a fairly major restriction. Essentially it means
that shared
(static) libraries are no use, because you have to build them into
the build
folder of the application that uses them, and therefore can't
easily use them
in more than one application. We have a number of applications that
link with
the same shared libraries.
When I originally set up our Xcode projects for 2.0, I ended up using
a common build directory for everything to overcome the problem it
had with not separating Debug and Release builds into separate
directories. I've stuck with that scheme, except that I no longer
explicitly add "Debug" or "Release" to the path, so we end up with,
say, Build/Debug/ containing
For us this works quite well, but I don't know how well it'd work for
you.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/xcode-users/email@hidden
