On Feb 22, 2008, at 3:15 PM, Chris Espinosa wrote:
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.
I presume by dragging the Nano.xcodeproj file from the finder and into
my Files list, I've accomplished this step.
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.)
How do I do this? Once I've done step 1, I can dink open
Nano.xcodeproj (the "second project") and see libNano.a with a little
carrying case icon next to it. However, the get-info for both of these
does not allow me to add to a target.
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.
How do I do this? I don't see the targets for the second project
anywhere. Obviously they are in the actual project…am I supposed to
open it and drag one of those targets to my project? (In CodeWarrior,
a nested project's targets showed up in the UI for the owning project).
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.
No, that's fair. Those steps are fine, but for the problems I have
above.
TIA,
--
Rick
_______________________________________________
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
