[Numpy-discussion] Building universal (fat) OS X binaries with numpy distutils

[Zachary Pincus]

> On Mon, May 26, 2008 at 1:35 PM, Zachary Pincus <zachary.pincus at yale.edu 
> > wrote:
>> Hello all,
>>
>> I'm wondering if anyone could let me know what the current "best
>> practices" are for building universal python extensions on OS X with
>> numpy's distutils and fortran code.
>>
>> Currently, I've been doing what this message suggests:
>> http://mail.python.org/pipermail/pythonmac-sig/2007-June/018986.html
>>
>> That is, get gfortran from http://r.research.att.com/tools/ , copy
>> libgfortran.a to somewhere different like ~/staticlibs/, and then do
>> this to build:
>>
>> export LDFLAGS="-undefined dynamic_lookup -bundle -arch i386 -arch  
>> ppc
>> -Wl,-search_paths_first"
>>
>> python setup.py config_fc --fcompiler=gnu95 --arch="-arch i386 -arch
>> ppc"
>> build_ext -L ~/staticlibs/ build
>>
>> Is this still the best bet?
>
> Yes. Have you had any problems with it?

No problems, but I just wanted to make sure that there wasn't now a  
simpler way already rolled in to the distutils or something, and to  
also make sure that there weren't some previously-discovered subtle  
problems with that method.

>> Also, how best should one get python
>> itself to compile as universal? (For py2app purposes...)
>
> Just us the binary from www.python.org. Is this not possible for  
> your use case?

I can, but I often build Python myself and I was just wondering how  
one does it. I can check elsewhere about this, though -- it's a bit  
off-topic for this list, I guess.

Thanks,
Zach