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.
(Is this documented anywhere?)
Presumably these linking problems would be overcome if we turned our static
libraries into private frameworks. However there would still be cross-project
references, as the main application's project would still have dependencies
on the framework targets. You certainly wouldn't want to have to build the
framework in the same location as the main application. Would you anticipate
any futher problems in this case?
Thanks,
James
_______________________________________________
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
