"M.-A. Lemburg" <mal at egenix.com> writes: > I just tried to compile some extensions on Win XP with .NET 1.1 > and Python 2.4c1 installed. > > It turns out that the distutils recognition logic for finding > a suitable C compiler is not able to find the compiler by simply > looking at the PATH, INCLUDE and LIB settings of the OS instead > of poking around in the registry :-) > > Now since extensions for 2.4 will have to be built using the > same compiler as Python itself (the one that comes with VC7.1 > which is the same as the one in the freely downloadable > .NET 1.1 SDK), I would suggest to make distutils aware of the > compiler by looking on the PATH in case the registry doesn't > have the VC7.1 entries. I always wondered if non-present registry entries wouldn't mean that the MSVC installation is broken. OTOH, I always used the official MS IDEs, and never tried their free compilers - is this desire related to the free ones? Thomas
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