To Framework or to Dylib?
To Framework or to Dylib?
- Subject: To Framework or to Dylib?
- From: Dave Thorup <email@hidden>
- Date: Wed, 23 Mar 2005 17:45:46 -0500
I'm in the process of converting a bunch of CFM shared libraries to
Mach-o. I've done all the hard stuff and currently have them built as
static libraries, but I want to make dynamic versions of them. Right
now I don't know whether to create just dynamic libraries (dylib) or to
create private Frameworks.
These libraries are private and I won't be distributing header files to
anyone and they don't contain any resources (images, Rez, text files,
etc.), just code. No matter what I create they'll be privately
embedded in the Application's bundle (@executable_path/../Frameworks)
and no one else will have access to them. There will be one or two
applications that will be using them.
So, I'm asking the list, which is better and why? Should I just create
dylibs or should I create Frameworks? What are the strengths and
weaknesses of each?
My initial feeling is that Frameworks provide more than what I need and
it would be more of a hassle to create Frameworks than to just create
dylibs. Maybe someone can provide arguments as to why Frameworks would
be a better choice.
Thanks!
PS I tried searching for previous discussions on this topic, but I
couldn't find any. If you know of any such discussions please point me
to them.
_____________________________
Dave Thorup
Software Engineer
email@hidden
http://www.kuwan.net
Defaults Manager - The premier editor for Mac OS X's User Defaults /
Preferences database.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden