setup.py Choosing Older Compiler On Windows

Ami Tavory atavory at gmail.com
Mon Dec 3 11:52:32 CET 2012


From: Irmen de Jong <irmen.NOSPAM at xs4all.nl>
>> To: python-list at python.org
>> Cc:
>> Date: Mon, 03 Dec 2012 01:10:23 +0100
>> Subject: Re: setup.py Choosing Older Compiler On Windows
>> On 2-12-2012 22:06, Dave Angel wrote:
>> > On 12/02/2012 09:34 AM, Ami Tavory wrote:
>> >>   Hello,
>> >>
>> >>   I'm porting a C++ extension module to a Windows machine >> that has
both VC8
>> >> and VC10 installed. Unfortunately, `setup.py build` tries to build >>
using
>> >> VC8, which fails (the extension uses C++ standard libraries >> that
VC  didn't
>> >> used to have). Is there a way to get setup.py to use VC10 >>
(preferably
>> >> externally, without modifying the script)?
>> >>
>> >>
>> >
>> > I haven't had to do Windows C++ development for many years, >> but
there
>> > used to be a vcvars.bat  in each compiler installation, and you >> run
the
>> > one corresponding to the compiler & libraries you want.
>>
>>
>> Forcing it to use a different compiler than the one that was used to >>
build Python
>> itself, may very well lead to a non-working extension module.
>>
>> Irmen

  Dave, Irmen,

  Many thanks for your answers - much appreciated!

  Got cvcars.bat to work in the sense that calling the compiler from the
command line resulted in the newer one being called, but setup.py for some
reason persisted in calling the older one. So due to Irmen's concern, this,
and other issues, I just hacked away the C++11 stuff and used the old
compiler.

  Many thanks,

  Ami
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/python-list/attachments/20121203/a7577037/attachment.html>


More information about the Python-list mailing list