Comments on: Intel and Pre-Tiger Compatibility http://mjtsai.com/blog/2005/06/07/intel-and-pre-tiger-compatibility/ Sun, 07 Sep 2008 01:06:26 +0000 http://wordpress.org/?v=2.5.1 By: Eric Albert http://mjtsai.com/blog/2005/06/07/intel-and-pre-tiger-compatibility/#comment-8213 Eric Albert Thu, 09 Jun 2005 09:29:38 +0000 /?p=1050#comment-8213 It's a little messy to do this in Xcode, but you can build the PowerPC side of your binary with whatever compiler you want, build the Intel side with GCC 4.0, and use lipo to create a universal binary from the two. The PPC side will then run back to whatever OS version that compiler version supports, and the Intel version will run on Apple's Intel systems. Obviously, if you'd like a better development experience for this or you'd like to be able to use GCC 4.0 to target earlier releases, file a bug report with Apple. It's a little messy to do this in Xcode, but you can build the PowerPC side of your binary with whatever compiler you want, build the Intel side with GCC 4.0, and use lipo to create a universal binary from the two. The PPC side will then run back to whatever OS version that compiler version supports, and the Intel version will run on Apple's Intel systems.

Obviously, if you'd like a better development experience for this or you'd like to be able to use GCC 4.0 to target earlier releases, file a bug report with Apple.

]]> By: Nat Irons http://mjtsai.com/blog/2005/06/07/intel-and-pre-tiger-compatibility/#comment-8211 Nat Irons Wed, 08 Jun 2005 20:00:42 +0000 /?p=1050#comment-8211 Sure, it's bad form for developers to dictate their customers' OS versions, but encouraging users to stick with earlier versions of 10.3 seems tantamount to encouraging them not to worry their pretty little heads about security releases. Limiting future 10.3 support to 10.3.9 strikes me as the responsible thing for Apple and third-party developers alike. I can say this because I don't know of any concrete reason why one might choose to stick with 10.3.8, outside of some glitches in Safari 1.3. Supporting Jaguar with a universal binary would be nice, but Jaguar's going to be even less of a factor by the time Intel-based Macs make universal binaries practical for regular folks. Sure, it's bad form for developers to dictate their customers' OS versions, but encouraging users to stick with earlier versions of 10.3 seems tantamount to encouraging them not to worry their pretty little heads about security releases. Limiting future 10.3 support to 10.3.9 strikes me as the responsible thing for Apple and third-party developers alike.

I can say this because I don't know of any concrete reason why one might choose to stick with 10.3.8, outside of some glitches in Safari 1.3. Supporting Jaguar with a universal binary would be nice, but Jaguar's going to be even less of a factor by the time Intel-based Macs make universal binaries practical for regular folks.

]]> By: Craig Hockenberry http://mjtsai.com/blog/2005/06/07/intel-and-pre-tiger-compatibility/#comment-8210 Craig Hockenberry Wed, 08 Jun 2005 05:31:37 +0000 /?p=1050#comment-8210 Also filed a bug at http://bugreport.apple.com -- the more the merrier. Also filed a bug at http://bugreport.apple.com -- the more the merrier.

]]> By: Craig Hockenberry http://mjtsai.com/blog/2005/06/07/intel-and-pre-tiger-compatibility/#comment-8209 Craig Hockenberry Wed, 08 Jun 2005 05:28:56 +0000 /?p=1050#comment-8209 <a href="http://lists.apple.com/archives/xcode-users/2005/May/msg00687.html">This</a> hints that it may be possible to build a Universal Binary that works on 10.2. I fiddled around with it for a few hours and didn't have any luck -- still getting the libmx missing errors on Jaguar. From what I've seen in other mailing list messages, the root of the problem is GCC 4.0 having a dependency on the library -- and it's not there on Jaguar. -ch This hints that it may be possible to build a Universal Binary that works on 10.2.

I fiddled around with it for a few hours and didn't have any luck -- still getting the libmx missing errors on Jaguar.

From what I've seen in other mailing list messages, the root of the problem is GCC 4.0 having a dependency on the library -- and it's not there on Jaguar.

-ch

]]> By: Michael http://mjtsai.com/blog/2005/06/07/intel-and-pre-tiger-compatibility/#comment-8206 Michael Tue, 07 Jun 2005 14:52:25 +0000 /?p=1050#comment-8206 More from <a href="http://lists.apple.com/archives/Xcode-users/2005/Jun/msg00128.html">Chris Espinosa</a>. I guess I should read all the lists before posting. More from Chris Espinosa. I guess I should read all the lists before posting.

]]> By: Michael http://mjtsai.com/blog/2005/06/07/intel-and-pre-tiger-compatibility/#comment-8205 Michael Tue, 07 Jun 2005 14:48:57 +0000 /?p=1050#comment-8205 <a href="http://lists.apple.com/archives/Xcode-users/2005/Jun/msg00139.html">Greg Hurrell</a> had the same thought. Greg Hurrell had the same thought.

]]>