Bugs item #1508010, was opened at 2006-06-18 09:11 Message generated for change (Settings changed) made by loewis You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1508010&group_id=5470
Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Distutils Group: Python 2.5 Status: Open Resolution: None >Priority: 7 Submitted By: Jimmy Retzlaff (jretz) >Assigned to: Martin v. Löwis (loewis) Summary: msvccompiler.py using VC6 with Python 2.5a2 Initial Comment: The change in revision 42515 checks if MSSdk is defined, and if so it will "Assume that the SDK set up everything alright." The problem is that the SDK may be set up for a different version of cl.exe than is expected. In my case I have VC6 and VC7.1 installed and the SDK is set up for VC6. When building extensions for Python 2.5a2, distutils tries to use VC6 in my case. ---------------------------------------------------------------------- Comment By: Jimmy Retzlaff (jretz) Date: 2006-06-25 01:01 Message: Logged In: YES user_id=101588 There is an option when installing VC (or at least there used to be, I haven't checked lately) to set the environment variables to take effect system wide. This is useful in that the build environment is always available at any command line (and they are also set when I build from my editor which is not VS). I've left mine pointed at VC6 as I typically do standalone DLLs using VC6 so they are easier to redistribute. Distutils has always selected the right version so it hasn't been an issue for me when working on Python things before. The issue wouldn't be as difficult if the resulting behavior were more obvious. Unfortunately the initial errors in my case were syntax errors arising from macro definitions that changed between VC6 and VC7.1. Most of the time I spent updating py2exe to work with 2.5 was spent on diagnosing this. It wasnât helped by the fact that I had a blind spot regarding the compiler version. I use a batch file to build py2exe for 2.3, then 2.4, and finally 2.5. Since 2.3 and 2.4 were building fine I didnât even consider the idea of the wrong compiler version being used for quite a while. For now I just do "set MSSDK=" before building and then everything works just fine. ---------------------------------------------------------------------- Comment By: Martin v. Löwis (loewis) Date: 2006-06-24 12:30 Message: Logged In: YES user_id=21627 I don't understand the problem. MSSdk gets defined by opening a specific SDK build environment. Just don't open that build environment, but open a regular cmd.exe window, and it should work fine. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1508010&group_id=5470 _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
