site_archiver@lists.apple.com Delivered-To: darwin-dev@lists.apple.com On Oct 18, 2004, at 8:14 AM, Josh wrote: Shantonu, Thanks for the tips. I'll take a look at the odcctools project. There are a couple of reasons I don't want to include it as a framework. First of all, size is of the utmost importance so I wanted to have it statically linked into my executable and rely on the linker to strip out the dead code (I'm not even sure how well Codewarrior's linker does this, as I haven't gotten far enough to test this out). Second of all I didn't want to require a file on the user's system. In retrospect, the second isn't as big a problem (since my CFM app is bundled) as the first. A bundle has the advantage that you can rebuild and redistribute it independent of your main app, if necessary. Shantonu _______________________________________________ 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 didn't say "framework", but that's an option. If your app is already bundled, the user will never see the internal layout unless they try really hard. What makes you think static linking will make smaller code? The Xcode 1.5 tools release supports dead code stripping, which can be used for dylibs and bundles, as well as main executables. All you have to do is create an exports lists of the symbols you want to be visible. Anything that's not reachable from those entry points will be dead code stripped. This email sent to site_archiver@lists.apple.com