Zach Welch added the comment:
That's certainly an interesting data point. We are just beginning to use
MinGW-w64 internally, so I do not have enough experience to confirm or deny
that advice. For various reasons, we must use cross-compiling on a Linux host,
so the advice to use a native
Zach Welch added the comment:
Yes, pe-i386 and pe-x86-64 are the respective 32-bit and 64-bit object formats.
Your commands seem reasonable. With gendef, I just let it create a .def file
with the same name (i.e. skip the '-' and redirection); in my mind, that
reinforces the association
Zach Welch added the comment:
The libpython27.a is an actual 32-bit version, as confirmed by running objdump
-t on it. It reports the sections' file format as pe-i386 instead of
pe-x86-64. I am only using it for building for the 64-bit target, so I cannot
confirm its viability for 32-bit
New submission from Zach Welch:
I tried to link a program against the libpython27.a provided by the latest
2.7.9 amd64 installer, only to discover that the provided library is a 32-bit
version. I had to go through the gendef/dlltool dance in order to produce a
useable 64-bit library from
