Thank you everybody for your replies. I believe Renato's goal was to build pywin32 without the MSVC compiler, but I'm not sure he was done with that. Looking more carefully to his patch, it seems that he calls
"setup.py build --compiler=mingw32" to force compiler so I'll try that later. Le 18/11/2015 03:41, David Marceau a écrit : > On 11/17/2015 11:49 AM, Frédéric Wang wrote: >>> Hi Allan. Nuitka worked for me in the past for creating executables, but >>> the MSYS2 package was broken last time I checked. Pywin32 is work in >>> progress with several modules building already. I stopped at some error >>> about exception handling or something, and then I switched to ctypes and >>> didn't need pywin32 anymore. If someone is interested in continuing the >>> work maybe I can give some hints. >> Hi Renato, >> >> I want to run a buildbot slave in a MINGW 64/32 shells [1] and so need the >> pywin32 dependency. Could you please give me hints on how you start building >> pywin32 so that I can try to take over your work? >> >> What I tried so far is: >> - Download the archive of pywin32 version 219 [2] >> - Apply your latest patch [3] >> - run python setup.py build in a MINGW64 shell. I obtained the following >> error: >> [error: Python was built with Visual Studio version 6, and extensions need >> to be built with the same version of the compiler, but it isn't installed.] > If the error explicitly states needing MS Visual Studio version 6.0, you > will need to procure that version. That will get you to build it as is. > > If you trying to modernize it with a more recent MS Visual Studio, then > the headers/libraries associated with MS Visual Studio version 6.0 are > still necessary. Some but not all command line tools from MS Visual > Studio version 6.0 would be needed such as the resource compiler. > Once you find all the headers and libraries for that version and point > to your include/lib/resourcecompiler environment paths to get there, you > have a fighting chance at building it with the latest versions of ms dev > studio CL.exe and Link.exe. Make sure the 2006 > inc/libs/resource-compiler are first in the path if you're trying to > achieve this build. > > For MS Dev 2006, place "verbose" on for: > -MSBuild/MS IDE build > -CL.exe > -Link.exe > > For the MSYS side of things, also place verbosity for make, gcc, ld when > building pywin32. Keep in mind within gcc/g++ it hides the linker > verbosity turn it back on to better understand what gets linked and in > what order. If there are any bash scripts involved echo on so you can > see the commands executed. > > When you see ALL the steps involved in the build both on the windows > side and the linux/GNU side of things you'll have a better picture of > what exactly is wrong and what exactly needs to be fixed. > > I hope this helps. > > Cheers. > > ------------------------------------------------------------------------------ > _______________________________________________ > Msys2-users mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/msys2-users
signature.asc
Description: OpenPGP digital signature
------------------------------------------------------------------------------
_______________________________________________ Msys2-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/msys2-users
