Building Binary Packages

[kyosohma]

I am trying to figure out how to build binaries for Python packages
and I've done it with MinGW. However, in my research, I've noticed
that some of the programmers out there think that you should use the
compiler that is used to compile the official Python distributions,
which appears to be Visual Studio 2003.

None of these programmers has really given their reasons for this
though. Does compiling with a different compiler introduce subtle
issues of some sort? If so, what are they (in general)? If you don't
use VS2003, what compiler do you use?

Here are the some links to what I've been reading:

http://boodebr.org/main/python/build-windows-extensions
http://www.z3lab.org/sections/blogs/philipp-weitershausen/2007_07_26_cheap-binary-windows
http://www.gooli.org/blog/building-m2crypto-on-windows/

Thank you for your time.

Mike

 

[Jim B. Wilson]

I am trying to figure out how to build binaries for Python packages and
I've done it with MinGW.

Apparently, you still can: http://tinyurl.com/yb4bps

 

[kyosohma]

Apparently, you still can:http://tinyurl.com/yb4bps

That's a wealth of information. It'll take a while for me to grasp it
all, but thanks a lot! Maybe I'll compile with both for a while to see
if there's any obvious differences.

Mike

 

[kyosohma]

Apparently, you still can:http://tinyurl.com/yb4bps

I had an acquaintance look at that information who has way more
experience in compiling extensions than I do. He says:

"MinGW seems to usually link to msvcrt.dll and the Python
distributions link to msvcr71.dll. It might be possible to convince
MinGW to use msvcr71.dll by editing the specs config file but I think
it will still link to msvcrt.dll in some cases, possibly alongside
msvcr71.dll which makes this quite a mess to debug."

Does anyone know if this is an issue?

Mike