Thomas Heller <theller at python.net> writes: >> Ouch. One other thought I had, based on some comments from Gareth, was >> that getting distutils to work with the free MS compilers would be >> good. I'm not sure what would be involved, or if I could help (I'm not >> familiar with the distutils code, though...) > > Do you mean building the wininst.exe template with other compilers? > Shouldn't be needed, because the binaries are also in CVS. Nope. I'm talking about the "build_ext" command. I have MSVC6 installed, and the .NET framework MSVC7 compilers. If I have the free compilers in my PATH (I don't expect distutils to auto-detect the free compilers from the registry, as it does for MSVC6), and do python24 setup.py build, I get the error: >C:\Apps\Python24\python.exe setup.py build running build running build_py creating build creating build\lib.win32-2.4 copying alarm.py -> build\lib.win32-2.4 running build_ext error: Python was built with version 7.1 of Visual Studio, and extensions need to be built with the same version of the compiler, but it isn't installed. So even though I have the free VC7 compiler, and it's in my PATH, I still can't build a simple extension with it. Even renaming the MSVC6 registry key, to get it out of the way, didn't help. Also, distutils adds optimisation flags to the command line, which don't work with the free compilers. Etc, etc. I suspect it's possible, but non-trivial, to get it working. I'm not sure I understand distutils well enough to risk attempting to get it right :-( Paul. -- This signature intentionally left blank
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