site_archiver@lists.apple.com Delivered-To: darwin-dev@lists.apple.com On Mar 20, 2005, at 5:46 PM, Michael B Allen wrote: _______________________________________________ Do not post admin requests to the list. They will be ignored. Darwin-dev mailing list (Darwin-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/darwin-dev/site_archiver%40lists.appl... I have a library of generic C modules (e.g. hashmap, allocator, csv parser, etc) [1] that I have ported to OS X. At least it compiles cleanly. Now I need to figure out how to package it. My question is - should I create a Framework or just a standard UNIX style shared library to go in /usr/lib? In either case I'm just using a straight forward Makefile at this point. My code is just POSIX level stuff (mostly ANSI C actually). Can someone provide a pointer to a Makefile that illustrates how to correctly build a dylib and/or Framework? dylibs are easy; pretty similar to shared libraries on other platforms. Use 'libtool', 'ld -dylib', or 'gcc -nostartfiles -Wl,-dylib' to make the library. I can't help with Frameworks; whether you should make one or not probably depends on your target audience. If you're targeting other Unix-app porters, might as well stick with /usr/local/include and /usr/local/lib. If you're targeting people using XCode, etc, a Framework is probably a good idea. This email sent to site_archiver@lists.apple.com