[OS X TeX] asy (darwin)

Justin C. Walker justin at mac.com
Sun Jun 13 05:15:30 CEST 2010

On Jun 12, 2010, at 17:20 , Victor Ivrii wrote:

> On Sat, Jun 12, 2010 at 6:57 PM, Richard Koch  
> <koch at math.uoregon.edu> wrote:
>> Peter,
>> MacTeX probably has later binaries than TeX Live, because I  
>> compiled binaries, made a new MacTeX pretest,
>> and then asked Karl if I should submit those binaries to TeX Live.  
>> Karl said that sources would
>> change again in two days, so we are waiting until everything  
>> stabilities before compiling
>> and updating the Mac binaries in TeX Live.
> Yes - MacTex 06/04 had 1.94 but then there was a flurry of version
> changes with very short lived 1.95, and then 1.96 stable as of
> 2010-06-07, 1.97 stable as of today and 1.98 already passing through
> few revisions
> BTW, how to compile for both intel _32 and _64?

There are a couple of ways to get a "universal" app.

1) Use the magic of Xcode: set up a project for this and other  
commands you want to be universal, and then, under build settings,  
select the architectures you want.  Details are beyond the scope of  
this list :-}.  I think the doc for Xcode will give you some assistance.

2) Given that you have two versions (_32, _64), you can "lipo" them  
together as a universal object file.

If the command is "simple" (no libraries other than system-supplied  
ones), this builds 'cmd' as universal:
   cc -arch x86_64 -arch i386 cmd.c -o cmd

If the command requires non-system libraries (e.g., ones you build  
yourself), then your best bet is to build them separately, and then  
use "lipo" directly:
   lipo -arch i386 cmd-i386 -arch x86_64 cmd-x86_64 -output cmd -create
The "-arch xxx" bits are actually redundant; lipo figures this out for  
itself if you don't help.



Justin C. Walker
Network, n., Difference between work
charged for and work done

More information about the macostex-archives mailing list