Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.python > #21987 > unrolled thread
| Started by | Ralph Heinkel <ralph.heinkel@web.de> |
|---|---|
| First post | 2012-03-21 08:06 -0700 |
| Last post | 2012-03-22 08:06 +0100 |
| Articles | 7 — 6 participants |
Back to article view | Back to comp.lang.python
Compiling Python (modules) on 64bit Windows - which compiler suite? Ralph Heinkel <ralph.heinkel@web.de> - 2012-03-21 08:06 -0700
Re: Compiling Python (modules) on 64bit Windows - which compiler suite? Terry Reedy <tjreedy@udel.edu> - 2012-03-21 13:56 -0400
Re: Compiling Python (modules) on 64bit Windows - which compiler suite? Dennis Lee Bieber <wlfraed@ix.netcom.com> - 2012-03-21 15:02 -0400
Re: Compiling Python (modules) on 64bit Windows - which compiler suite? Thomas Bach <thbach@students.uni-mainz.de> - 2012-03-21 20:03 +0100
Re: Compiling Python (modules) on 64bit Windows - which compiler suite? cjgohlke@gmail.com - 2012-03-21 17:06 -0700
Re: Compiling Python (modules) on 64bit Windows - which compiler suite? Ralph Heinkel <ralph.heinkel@web.de> - 2012-03-22 11:34 -0700
Re: Compiling Python (modules) on 64bit Windows - which compiler suite? Stefan Behnel <stefan_ml@behnel.de> - 2012-03-22 08:06 +0100
| From | Ralph Heinkel <ralph.heinkel@web.de> |
|---|---|
| Date | 2012-03-21 08:06 -0700 |
| Subject | Compiling Python (modules) on 64bit Windows - which compiler suite? |
| Message-ID | <808abad4-3ab3-4336-8a31-2f88eb28be01@v22g2000vby.googlegroups.com> |
Hi, when processing our mass spectrometry data we are running against the 2GB memory limit on our 32 bit machines. So we are planning to move to 64bit. Downloading and installing the 64bit version of Python for Windows is trivial, but how do we compile our own C extension? Visual C ++ 2008 express comes for free, but only compiles for 32 bit. What has been used to compile the downloadable Python Win64 bit version? Visual Studio professional? The problem with the professional edition is that it is hard to obtain and it is sort of out-of-date - nowadays everyone uses Visual Studio 2010 (or even 2011 coming soon). So if Visual Studio 2008 professional is required for compiling 64bit modules, we would have to spend $1200 for a license which is actually rather out of date. Any hints or suggestions are very welcome. Thanks, Ralph
[toc] | [next] | [standalone]
| From | Terry Reedy <tjreedy@udel.edu> |
|---|---|
| Date | 2012-03-21 13:56 -0400 |
| Message-ID | <mailman.868.1332352612.3037.python-list@python.org> |
| In reply to | #21987 |
On 3/21/2012 11:06 AM, Ralph Heinkel wrote: > when processing our mass spectrometry data we are running against the > 2GB memory limit on our 32 bit machines. So we are planning to move to > 64bit. Downloading and installing the 64bit version of Python for > Windows is trivial, but how do we compile our own C extension? Visual C > ++ 2008 express comes for free, but only compiles for 32 bit. > > What has been used to compile the downloadable Python Win64 bit > version? Visual Studio professional? Yes. Python Windows devs get it for free from MS. > The problem with the professional edition is that it is hard to obtain > and it is sort of out-of-date - nowadays everyone uses Visual Studio > 2010 (or even 2011 coming soon). So if Visual Studio 2008 professional > is required for compiling 64bit modules, we would have to spend $1200 > for a license which is actually rather out of date. > > Any hints or suggestions are very welcome. I believe the intention is to release 3.3 compiled with VS 2010. Brian Curtin and Martin Loewis are working on that. I believe people have successfully built at least the basics with VS2010. You could also dual boot to Linux and get 64 bit gcc for free. -- Terry Jan Reedy
[toc] | [prev] | [next] | [standalone]
| From | Dennis Lee Bieber <wlfraed@ix.netcom.com> |
|---|---|
| Date | 2012-03-21 15:02 -0400 |
| Message-ID | <mailman.871.1332356537.3037.python-list@python.org> |
| In reply to | #21987 |
On Wed, 21 Mar 2012 08:06:47 -0700 (PDT), Ralph Heinkel
<ralph.heinkel@web.de> declaimed the following in
gmane.comp.python.general:
> Hi,
>
> when processing our mass spectrometry data we are running against the
> 2GB memory limit on our 32 bit machines. So we are planning to move to
> 64bit. Downloading and installing the 64bit version of Python for
> Windows is trivial, but how do we compile our own C extension? Visual C
> ++ 2008 express comes for free, but only compiles for 32 bit.
>
I believe the 64-bit compilers are available in the .NET SDK... You
then need to configure Express to find them.
http://msdn.microsoft.com/en-us/library/9yb4317s%28v=vs.90%29.aspx
--
Wulfraed Dennis Lee Bieber AF6VN
wlfraed@ix.netcom.com HTTP://wlfraed.home.netcom.com/
[toc] | [prev] | [next] | [standalone]
| From | Thomas Bach <thbach@students.uni-mainz.de> |
|---|---|
| Date | 2012-03-21 20:03 +0100 |
| Message-ID | <mailman.872.1332356657.3037.python-list@python.org> |
| In reply to | #21987 |
Hi,
Ralph Heinkel <ralph.heinkel@web.de> writes:
> Hi,
>
> when processing our mass spectrometry data we are running against the
> 2GB memory limit on our 32 bit machines. So we are planning to move to
> 64bit. Downloading and installing the 64bit version of Python for
> Windows is trivial, but how do we compile our own C extension?
What about installing Cygwin and using the shipped GCC?
Regards,
Thomas Bach.
[toc] | [prev] | [next] | [standalone]
| From | cjgohlke@gmail.com |
|---|---|
| Date | 2012-03-21 17:06 -0700 |
| Message-ID | <13033772.7.1332374778471.JavaMail.geo-discussion-forums@ynjk1> |
| In reply to | #21987 |
On Wednesday, March 21, 2012 8:06:47 AM UTC-7, Ralph Heinkel wrote: > Hi, > > when processing our mass spectrometry data we are running against the > 2GB memory limit on our 32 bit machines. So we are planning to move to > 64bit. Downloading and installing the 64bit version of Python for > Windows is trivial, but how do we compile our own C extension? Visual C > ++ 2008 express comes for free, but only compiles for 32 bit. > > What has been used to compile the downloadable Python Win64 bit > version? Visual Studio professional? > The problem with the professional edition is that it is hard to obtain > and it is sort of out-of-date - nowadays everyone uses Visual Studio > 2010 (or even 2011 coming soon). So if Visual Studio 2008 professional > is required for compiling 64bit modules, we would have to spend $1200 > for a license which is actually rather out of date. > > Any hints or suggestions are very welcome. > > Thanks, > > Ralph See "Compiling 64-bit extension modules on Windows" at <http://wiki.cython.org/64BitCythonExtensionsOnWindows>. It applies to non-Cython extensions as well. MinGW-w64 also works, but you'll have to generate and use libpythonXX.a and libmsvcr90.a link libraries. Christoph
[toc] | [prev] | [next] | [standalone]
| From | Ralph Heinkel <ralph.heinkel@web.de> |
|---|---|
| Date | 2012-03-22 11:34 -0700 |
| Message-ID | <11748169.44.1332441298178.JavaMail.geo-discussion-forums@vbbp15> |
| In reply to | #22005 |
> > See "Compiling 64-bit extension modules on Windows" at <http://wiki.cython.org/64BitCythonExtensionsOnWindows>. It applies to non-Cython extensions as well. > > MinGW-w64 also works, but you'll have to generate and use libpythonXX.a and libmsvcr90.a link libraries. > > Christoph Thanks to everyone who has replied to my question. Especially for the link/hint to use the .NET SDK which indeed seems to provide the right tools for 64bit compilation. I'm going to try this and report back here. Cheers, Ralph
[toc] | [prev] | [next] | [standalone]
| From | Stefan Behnel <stefan_ml@behnel.de> |
|---|---|
| Date | 2012-03-22 08:06 +0100 |
| Message-ID | <mailman.878.1332399996.3037.python-list@python.org> |
| In reply to | #21987 |
Thomas Bach, 21.03.2012 20:03: > Ralph Heinkel writes: >> when processing our mass spectrometry data we are running against the >> 2GB memory limit on our 32 bit machines. So we are planning to move to >> 64bit. Downloading and installing the 64bit version of Python for >> Windows is trivial, but how do we compile our own C extension? > > What about installing Cygwin and using the shipped GCC? I'm pretty sure it doesn't cross compile to native Windows. It certainly won't build against a native Windows Python installation, and given the overhead that cygwin induces into a lot of common OS operations (such as fork(), I/O operations or file system access), a native Windows Python installation has serious advantages in most cases. If the choice is GCC, then MinGW is the right tool. Stefan
[toc] | [prev] | [standalone]
Back to top | Article view | comp.lang.python
csiph-web