Proper way to compile static libraries into projects?
Proper way to compile static libraries into projects?
- Subject: Proper way to compile static libraries into projects?
- From: Army Research Lab <email@hidden>
- Date: Tue, 20 Nov 2007 08:35:32 -0500
- Thread-topic: Proper way to compile static libraries into projects?
This is very simple question, but one I want to do right to simplify my
upgrade path.
I am currently tied to OS X 10.4 and Xcode 2.4 (Xcode IDE: 759.0, Xcode
Core: 757.0, ToolSupport: 733.0). I have just started a new project that
includes a great deal of legacy code, and a number of third party libraries.
The libraries are blobs of source code, along with a slew of compile
instructions, but no makefiles or other build files. To help organize
things, I would like to have a single project with many different targets.
I want each of the libraries to be statically linked (I'm targeting an
embedded system, there's no point in anything else), and I want to have one
target for each main that I have (unit test driver main, application main,
etc.) I'm hoping that this will help keep the madness down to a manageable
level.
My question are thus:
1) Is this is the best way to organize things?
2) How do I tell Xcode that one target is dependent on one or more other
targets? Basically, how do I get the libfoo.a referenced in my main target
when it hasn't been built yet?
3) Is there anything special I have to do to link everything together? I
already have the header files in the project, but it would quite handy to
pretend that they are all packaged together with the library, even though it
won't actually be installed on any system.
Please keep in mind that I do intend to upgrade to Leopard and Xcode 3.0
ASAP, but that ASAP may be at least a few months down the road.
Thanks,
Cem Karan
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden