library dependancies
library dependancies
- Subject: library dependancies
- From: Brian Barnes <email@hidden>
- Date: Thu, 29 Apr 2004 00:00:52 -0400
I'm experimenting with archives and dylibs ... trying to find the best
format to use for my applications that share a lot of common code, and
also to cut development time by making the applications compile faster
by dynamically linking (therefore I'm moving the dylibs.)
I'm not the expert on this, and I just think I'm missing how to
statically link stuff together.
For instance, I have one dylib that needs a archive (.a) and a
framework (IOKit) in it. This dylib is then put into an application.
Well, the application needs both the .a and the framework for IOKit
(which is actually needed by the .a) for it to compile, even though
these are only needed by the original dylib.
I want these dylibs to be self contained and not need to have their
frameworks or .a (or included dylibs) need to be put into the main app.
Pointing me at the correct docs or the correct dialogs is probably all
I need!
Thanks ...
[>] Brian
_______________________________________________
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.