site_archiver@lists.apple.com Delivered-To: darwin-kernel@lists.apple.com User-agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.1.9) Gecko/20100317 Thunderbird/3.0.4 Chris, Thanks -- I stand corrected. Thanks, -Ryan Hi Ryan, On Mon, May 3, 2010 at 11:18 PM, Ryan Hankins<rqh@small-tree.com> wrote: No, this is incorrect. You have to do what you say if you want to use the newer features (weak linking was only introduced in 10.6), but if that isn't the case, you can build a single Universal binary (by using the 10.6 SDK for x86_64 and 10.4 SDK for everything else). We do exactly that and it works fine—there’s another post of mine to this list somewhere that describes what I did to make it work. Kind regards, Chris -- Ryan Hankins Software Engineer Small Tree Communications www.small-tree.com rqh@small-tree.com +1 651 209-6509 x303 _______________________________________________ Do not post admin requests to the list. They will be ignored. Darwin-kernel mailing list (Darwin-kernel@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/darwin-kernel/site_archiver%40lists.a... So, you must be able to glue the two things together with the lipo command once they've been built against separate SDKs... interesting. In other words, as long as you are supporting only 10.4 APIs (that are still available on 10.6), you can do this. Basically, you can't build a single universal binary. You have to build separate kexts and either install both of them or else use the PlugIns directory to build it into one "package." See: This email sent to site_archiver@lists.apple.com