[Python-Dev] python, lipo and the future?

Ronald Oussoren ronaldoussoren at mac.com
Sun Sep 17 20:53:03 CEST 2006

On Sep 17, 2006, at 8:35 PM, Martin v. Löwis wrote:

> Josiah Carlson schrieb:
>> "Martin v. Löwis" <martin at v.loewis.de> wrote:
>>> Out of curiosity: how do the current universal binaries deal with  
>>> this
>>> issue?
>> If I remember correctly, usually you do two completely independant
>> compile runs (optionally on the same machine with different  
>> configure or
>> macro definitions, then use a packager provided by Apple to merge the
>> results for each binary/so to be distributed. Each additional  
>> platform
>> would just be a new compile run.
> It's true that the compiler is invoked twice, however, I very much  
> doubt
> that configure is run twice. Doing so would cause the Makefile being
> regenerated, and the build starting from scratch. It would find the
> object files from the previous run, and either all overwrite them, or
> leave them in place.
> The gcc driver on OSX allows to invoke cc1/as two times, and then
> combines the resulting object files into a single one (not sure  
> whether
> or not by invoking lipo).

IIRC the gcc driver calls lipo when multiple -arch flags are present  
in the command line. This is very convenient, especially when  
combined with distutils. Universal builds of Python will automaticly  
build universal extensions as well, without major patches to distutils.


-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 2157 bytes
Desc: not available
Url : http://mail.python.org/pipermail/python-dev/attachments/20060917/bb04a59f/attachment.bin 

More information about the Python-Dev mailing list