On Feb 22, 2008, at 6:15 PM, Chris Espinosa wrote:
In three separate and semantically distinct steps.
1) Add the project reference. This simply allows you access to the
other project's targets and build products. It does not create
dependencies or cause linking.
2) Add one of the second project's build products to a target in
your project. This will cause your target to be linked against it,
and if it's a framework, compiled against its headers. (If it's not
a framework, you have to set your Header Search Paths to find its
headers; that's one of the things frameworks are for.)
3) Add the target that builds that build product to your target's
dependencies. This causes that build product to be built if needed
when your target is built.
If you ask why Xcode doesn't do all that for you, it should, but
there are valid reasons to do only one or two of the three and not
the others, so it's not possible to make it fully automatic /and/ do
what you want all the time.
It would seem that one could devise a dialog that would open when a
project is added to another project that would ask the appropriate
questions to determine what the user wants from among these choices
and then does the appropriate thing. Something along the lines of the
New project dialog or the What targets do you want to add this file
to? dialog or some other Wizard UI should be possible to both make
this an easier process and allow it to be fully customizable.
--
Brian Stern
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:
http://lists.apple.com/mailman/options/xcode-users/email@hidden
