Export to GitHub

caseman - issue #2

build install on vista


Posted on Jun 16, 2009 by Massive Giraffe

What steps will reproduce the problem? 1. python setup.py install

What is the expected output? What do you see instead?

I'd expect the package to install to my c:\Python26 packages dir.

What version of the product are you using? On what operating system?

1.0b3

Please provide any additional information below.

Hi I've downloaded your noise and tried to install it via python setup.py install and get an error 'error: Unable to find vcvarsall.bat'.

After a bit of googling I'm under the impression i need visual studio installed for that bat file. Is visual studio required for install?

Can I install just the python part without the C libraries?

thanks!

Comment #1

Posted on Jun 16, 2009 by Massive Giraffe

Actually here is the full error:

pink@ganj ~/noise-1.0b3 $ python setup.py install running install running build running build_py running build_ext building 'noise._simplex' extension error: Unable to find vcvarsall.bat

Comment #2

Posted on Jun 16, 2009 by Swift Camel

Yes, python requires a compiler (visual studio by default) to compile C libraries on windows. Did you try the noise binary for windows available here?

http://caseman.googlecode.com/files/noise-1.0b3.win32-py2.6.exe

It does require python 2.6, which happens to be much easier for compiling libs on windows than 2.5 was.

Comment #3

Posted on Sep 10, 2011 by Helpful Ox

I had that problem too, but now on python 2.7 i get this problem after i installed visual studio c++ 2008(2010 didn't work...):

running install running build running build_py creating build creating build\lib.win32-2.7 creating build\lib.win32-2.7\noise copying perlin.py -> build\lib.win32-2.7\noise copying shader.py -> build\lib.win32-2.7\noise copying shader_noise.py -> build\lib.win32-2.7\noise copying init.py -> build\lib.win32-2.7\noise running build_ext building 'noise._simplex' extension Traceback (most recent call last): File "C:\Users\pbsds\Desktop\noise-1.0b3\setup.py", line 54, in extra_compile_args=compile_args, File "C:\Python27\lib\distutils\core.py", line 152, in setup dist.run_commands() File "C:\Python27\lib\distutils\dist.py", line 953, in run_commands self.run_command(cmd) File "C:\Python27\lib\distutils\dist.py", line 972, in run_command cmd_obj.run() File "C:\Python27\lib\distutils\command\install.py", line 563, in run self.run_command('build') File "C:\Python27\lib\distutils\cmd.py", line 326, in run_command self.distribution.run_command(command) File "C:\Python27\lib\distutils\dist.py", line 972, in run_command cmd_obj.run() File "C:\Python27\lib\distutils\command\build.py", line 127, in run self.run_command(cmd_name) File "C:\Python27\lib\distutils\cmd.py", line 326, in run_command self.distribution.run_command(command) File "C:\Python27\lib\distutils\dist.py", line 972, in run_command cmd_obj.run() File "C:\Python27\lib\distutils\command\build_ext.py", line 340, in run self.build_extensions() File "C:\Python27\lib\distutils\command\build_ext.py", line 449, in build_extensions self.build_extension(ext) File "C:\Python27\lib\distutils\command\build_ext.py", line 499, in build_extension depends=ext.depends) File "C:\Python27\lib\distutils\msvc9compiler.py", line 473, in compile self.initialize() File "C:\Python27\lib\distutils\msvc9compiler.py", line 383, in initialize vc_env = query_vcvarsall(VERSION, plat_spec) File "C:\Python27\lib\distutils\msvc9compiler.py", line 299, in query_vcvarsall raise ValueError(str(list(result.keys()))) ValueError: [u'path']

HALP!

Comment #4

Posted on Sep 12, 2011 by Swift Camel

I'm not a windows compiler user, but this python bug sheds some light: http://bugs.python.org/issue7511

Notably:

"Martin v. Löwis (loewis) * Date: 2010-12-23 13:43 IIUC, the issue is that people installing a 64-bit Python, and VS Express, and then wonder why they can't build extension modules. I'm not so sure that there is a bug in Python here - this setup is not supported (and that's really Microsoft's fault). Now, automatically finding the SDK would be a new feature, IMO: if you want to use SDK tools, you are supposed to set DISTUTILS_USE_SDK, after opening the respective build environment. IIUC, installing VS express would not have been necessary in this setup at all - just install the SDK.

Alternatively, people can install Visual Studio proper, or use a 32-bit Python."

So it seems to be a problem with distutils finding the proper compiler when multiple compilers are installed. I am not in a position to fix this bug myself, but if you find a solution, please let me know.

Status: WontFix

Labels:
Type-Defect Priority-Medium OpSys-Windows