On Sep 17, 2006, at 8:35 PM, Martin v. Löwis wrote:
Josiah Carlson schrieb:"Martin v. Löwis" <[EMAIL PROTECTED]> wrote:Out of curiosity: how do the current universal binaries deal with thisissue?If I remember correctly, usually you do two completely independantcompile runs (optionally on the same machine with different configure ormacro definitions, then use a packager provided by Apple to merge theresults for each binary/so to be distributed. Each additional platformwould just be a new compile run.It's true that the compiler is invoked twice, however, I very much doubtthat 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 thencombines the resulting object files into a single one (not sure whetheror 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.
Ronald
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
