Welcome to the MacNN Forums.

If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below.

You are here: MacNN Forums > Software - Troubleshooting and Discussion > Applications > First 3rd Party Fat... err Universal Binary

First 3rd Party Fat... err Universal Binary
Thread Tools
Mac Elite
Join Date: May 2001
Location: Cambridge UK
Status: Offline
Reply With Quote
Jun 9, 2005, 03:46 PM
 
Talacia's Tag

This is the first one I've seen. Now, perhaps not significant in itself but I think evidence of how Cocoa apps will be ported in no time at all.

[Firefox and Mathematica obviously precede this, but you can't download either yet]
     
Addicted to MacNN
Join Date: Aug 2004
Location: FFM
Status: Offline
Reply With Quote
Jun 9, 2005, 04:01 PM
 
It doesn't look like this contains i386 code.

Code:
localhost:~ TETENAL$ lipo -detailed_info /Users/TETENAL/Desktop/Tag/Tag.app/Contents/MacOS/Tag input file /Users/TETENAL/Desktop/Tag/Tag.app/Contents/MacOS/Tag is not a fat file Non-fat file: /Users/TETENAL/Desktop/Tag/Tag.app/Contents/MacOS/Tag is architecture: ppc
(Last edited by TETENAL; Jun 9, 2005 at 04:50 PM. )
     
Mac Elite
Join Date: Jul 2002
Status: Offline
Reply With Quote
Jun 9, 2005, 04:47 PM
 
Why would anyone release Universal binaries now anyway? All it does is increase the download size.
     
Mac Elite
Join Date: Aug 2001
Status: Offline
Reply With Quote
Jun 9, 2005, 05:10 PM
 
I agree. I've built Adium as a universal binary (well, tried to anyway. It wasn't feeling like compiling for PPC or x86 at that point), but it would be pointless to release it as one.
     
Addicted to MacNN
Join Date: Apr 2001
Location: The bottom of Cloud City
Status: Offline
Reply With Quote
Jun 9, 2005, 05:19 PM
 
Originally Posted by Thinine
Why would anyone release Universal binaries now anyway? All it does is increase the download size.
Cuz they want to be first.

"Ahhhhhhhhhhhhhhhh"
     
Grizzled Veteran
Join Date: Jun 2002
Status: Offline
Reply With Quote
Jun 10, 2005, 11:25 AM
 
Originally Posted by TETENAL
It doesn't look like this contains i386 code.

Code:
localhost:~ TETENAL$ lipo -detailed_info /Users/TETENAL/Desktop/Tag/Tag.app/Contents/MacOS/Tag input file /Users/TETENAL/Desktop/Tag/Tag.app/Contents/MacOS/Tag is not a fat file Non-fat file: /Users/TETENAL/Desktop/Tag/Tag.app/Contents/MacOS/Tag is architecture: ppc
I haven't thought this Intel thing through, it means that Tag can't run on 10.3, so I think I'll wait a bit for actual Intel machines to appear to make it compatible , if any 10.3 users were experiencing problems with Tag 1.2.1, the new build available to download at:

http://www.talacia.com/download.php

should work fine. If it doesn't (I haven't had a chance to test it) then you can download Tag 1.2 (which works fine on 10.3 and is no different from 1.2.1, as they are Tiger fixes) at:

http://www.talacia.com/downloads/old/Tag.dmg

Thanks,
Oliver
     
Mac Elite
Join Date: Sep 2000
Location: Tempe, AZ
Status: Offline
Reply With Quote
Jun 10, 2005, 11:34 AM
 
Originally Posted by iOliverC
I haven't thought this Intel thing through, it means that Tag can't run on 10.3,
Binaries built using gcc 4.0 (universal binaries, in other words) are compatible with 10.3.9, but not with earlier versions of OS X. You can make a universal binary that is compatible with versions earlier than 10.3.9 by using gcc4 to compile the Intel side and gcc3.3 to compile the PPC side, and then using the 'lipo' command line tool to merge the two.

But really, there's no point in doing this today. What Steve showed at the keynote is preliminary; I assume things will change a bit before Apple ships an Intel box. Getting your code ready for Intel is good - shipping it today is pointless.
Geekspiff - generating spiffdiddlee software since before you began paying attention.
     
Grizzled Veteran
Join Date: Jun 2002
Status: Offline
Reply With Quote
Jun 10, 2005, 01:01 PM
 
Originally Posted by smeger
Binaries built using gcc 4.0 (universal binaries, in other words) are compatible with 10.3.9, but not with earlier versions of OS X. You can make a universal binary that is compatible with versions earlier than 10.3.9 by using gcc4 to compile the Intel side and gcc3.3 to compile the PPC side, and then using the 'lipo' command line tool to merge the two.

But really, there's no point in doing this today. What Steve showed at the keynote is preliminary; I assume things will change a bit before Apple ships an Intel box. Getting your code ready for Intel is good - shipping it today is pointless.
It was actually a coincidence that the Intel announcement came, I had planned to release a small .1 to fix a crasher, so I just added Intel support without thinking .

Thanks for the advice though, I'll need it for when Intel machines are out
     
Krypton  (op)
Mac Elite
Join Date: May 2001
Location: Cambridge UK
Status: Offline
Reply With Quote
Jun 17, 2005, 04:23 AM
 
Some more news:

• OmniGraffle 4: changed 2 lines of assembly code & recompile
• Stone iMaginator: an hours worth of work & recompile
     
Banned
Join Date: Jun 2003
Status: Offline
Reply With Quote
Jun 17, 2005, 09:10 AM
 
Originally Posted by Krypton
Some more news:

• OmniGraffle 4: changed 2 lines of assembly code & recompile
• Stone iMaginator: an hours worth of work & recompile
Things are looking bright for all the Cocoa apps and Carbon apps that were built strictly with OS X in mind.

I wonder how OS 9 -> Carbon apps are faring though. In any case, MS is almost certainly going to make everyone pay for the switch from PPC to x86, so I don't feel sorry if they have a lot of work to do with Office. Adobe might have a lot of work too moving everything to Xcode.

The next MSN Messenger (if the leaked pics are to be believed) is going to be Cocoa...so I'd be surprised if they had trouble making a Universal Binary of it...especially considering they probably have the Dev Kit right now and can make sure it compiles on both as they're working on it.

While I'm talking about MS, I'd love for the MacBU team to finally kill Media Player for Mac since it's garbage, and simply release a QuickTime plugin of their movie codecs.
     
   
Thread Tools
Forum Links
Forum Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On
Top
Privacy Policy
All times are GMT -5. The time now is 11:38 AM.
All contents of these forums © 1995-2011 MacNN. All rights reserved.
Branding + Design: www.gesamtbild.com
vBulletin v.3.8.7 © 2000-2011, Jelsoft Enterprises Ltd., Content Relevant URLs by vBSEO 3.3.2