A RetroSearch Logo

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Search Query:

Showing content from https://mail.python.org/pipermail/python-dev/2006-November/069918.html below:

[Python-Dev] Using SCons for cross-compilation

[Python-Dev] Using SCons for cross-compilation [Python-Dev] Using SCons for cross-compilationAnthony Baxter anthony at interlink.com.au
Thu Nov 9 07:45:30 CET 2006
On Thursday 09 November 2006 16:30, Martin v. Löwis wrote:
> Patch #841454 takes a stab at cross-compilation
> (for MingW32 on a Linux system, in this case),
> and proposes to use SCons instead of setup.py
> to compile extension modules. Usage of SCons
> would be restricted to cross-compilation (for
> the moment).
>
> What do you think?

So we'd now have 3 places to update when things change (setup.py, PCbuild 
area, SCons)? How does this deal with the problems that autoconf has with 
cross-compilation? It would seem to me that just fixing the extension module 
building is a tiny part of the problem... or am I missing something?

Anthony
-- 
Anthony Baxter     <anthony at interlink.com.au>
It's never too late to have a happy childhood.
More information about the Python-Dev mailing list

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4