RE: Links to other projects
RE: Links to other projects
- Subject: RE: Links to other projects
- From: "Bill Lowrey" <email@hidden>
- Date: Wed, 19 May 2004 18:06:45 -0500
- Organization: istation.com
With the project selected ( i.e. the root level of the tree ), right click
(errr - control-click if you have the default mouse), and choose Add ->
Existing Files... (or Existing Frameworks... ) and choose A.xcode. Then, Get
Info on the B_test target, and choose the little (+) sign under "Direct
Dependencies" on the "General" tab. Choose "A" from A.xcode, and you're
almost done.
Under the B_test target, make sure you have a Frameworks & Libraries Build
Phase. Then you can drag libA.a under it, and you're good.
This ignores a lot of more advanced uses, such as library ordering, and
selecting individual libs from a list of more than one. FWIW, I like to turn
on the Target Membership View (from View -> Groups & Files Columns -> Target
Membership) and use the visible checkboxes to include or exclude the libs in
my project. It's a lot easier to rearrange libs that way...
I managed to spend a week on this while trying to migrate some code from
MSVC, so I'd have to say it could be more obvious...
- Good luck!
- Bill Lowrey
Sr. Software Engineer
Istation.com
-----Original Message-----
From: email@hidden
[mailto:email@hidden] On Behalf Of Geoff Leyland
Sent: Wednesday, May 19, 2004 3:46 PM
To: email@hidden
Subject: Links to other projects
Hi,
I have an xcode project - A.xcode - that has several targets, one of
which build libA.a.
I have another project - B.xcode - which has a target B_test that links
to libA.a. I would add a target to B.xcode that will build A.xcode's
libA.a target before B_test is linked.
I've tried external targets (not the right thing), I've tried dragging
the the libA.a target from A.xcode to B.xcode (it *moves* the target!),
and option-dragging (finder shortcut for dragging a copy - doesn't
work) and command-option dragging (finder shortcut for dragging an
alias - doesn't work).
I suppose that I *could* create a duplicate of the the libA.a target
and copy it into B.xcode, but that really defeats the whole point of
having all build info libA.a in one place.
This is easy in Codewarrior and MSVC. Anyone know what I'm missing?
cheers,
Geoff
_______________________________________________
xcode-users mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/xcode-users
Do not post admin requests to the list. They will be ignored.
_______________________________________________
xcode-users mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/xcode-users
Do not post admin requests to the list. They will be ignored.