Re: setup.py Choosing Older Compiler On Windows
From: Irmen de Jong <irmen.NOSPAM@xs4all.nl>
>> To: firstname.lastname@example.org
>> 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
>> >> and VC10 installed. Unfortunately, `setup.py build` tries to build >>
>> >> VC8, which fails (the extension uses C++ standard libraries >> that
>> >> used to have). Is there a way to get setup.py to use VC10 >>
>> >> externally, without modifying the script)?
>> > I haven't had to do Windows C++ development for many years, >> but
>> > used to be a vcvars.bat in each compiler installation, and you >> run
>> > one corresponding to the compiler & libraries you want.
>> Forcing it to use a different compiler than the one that was used to >>
>> itself, may very well lead to a non-working extension module.
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
|All times are GMT. The time now is 02:50 PM.|
Powered by vBulletin®. Copyright ©2000 - 2013, vBulletin Solutions, Inc.
SEO by vBSEO ©2010, Crawlability, Inc.