Including additional link libraries by specifiying the libraries parameter in the Extension class call in setup.py fails, when using the MSVC compiler, the parameter silently gets ignored. This is caused by a bug in build_ext which has been introduced through the addition of cygwin support from 1.69 to 1.70 in 9/2000. "get_libraries" SHOULD return ext.libraries per default. Currently, it falls through and returns None, if the platform is WIN32 and the compiler is MSVCCompiler. I noticed this while trying to build the bsddb3 python extension for win32. A necessary library libdb40s was specified in setup.py, but the build failed because the value never got through to the linker. The attached patch adds a single "return ext.libraries" at the end of the case "win32", as a catch all. This fixes the problem.
Logged In: YES user_id=11105 The patch looks good. But I think you are wrong with the versions numbers. My Python 2.2.1 build_ext.py module doesn't seem to have this bug, it's version is 1.77.
Logged In: YES user_id=311771 Sourceforge currently doesn't display any versions to me ("There are 26 files, but none match the current tag ()"), so I can't check again. But I took a look into 1.77 from the Windows ActivePython python22 distro, instead . You are right: the "win32" has changed from "if win32 and msvc" if win32: if msvc return somewhere between 1.77 and now.
