Thanks Mark, >From the web page for the SDK I have. "This release of the SDK is intended to replace the Windows SDK for Vista." But this only appears to be 0x500 rather than 0x501. Hence my confusion. I get further confused when resetting the #define in win32credmodule.cpp has no effect. What's it there for? I had to debug setup.py to find the culprit and downgrade the windows_h_version required. Now win32cred builds OK, (no idea if it works but we'll ignore that for now) and my next problem is either missing files or missing variables depending on which of the three different, post Vista, SDK's I select. Along the way I've discovered far more than I ever wished to know about how setup.py and MSVC search directories and I have settled on using the MSSDK environment variable to attempt to synchronise them - again I don't know if it works because there doesn't seem to be a 'verbose' mode for setup.py. I appreciate that second guessing how MS names it's SDK's and where they get (randomly) installed is a mug's game so why attempt to duplicate and track it in setup.py? Surely trapping any MSVC errors and reporting them back would suffice? Even if I achieve a build, I'm not convinced that I'll be much better off. I find that one of the key benefits of building a project in the MSVC environment is that I can use 'goto definition' to unravel the structure of other peoples code. I'm deliberately lazy when getting to grips with 'new' stuff; I have enough to keep in my head about my own projects so all I want to know about the new stuff is 'Is it going to help me or hinder me?' and I want to find out with the minimum fuss and effort. I have to say that I'm disappointed with Pywin32 in that respect.so far.Almost everything I have tried to do, right from finding and downloading the sources has been less than obvious. What would help is: 1) certainty about exactly which MS SDK(s) are required including dates and recent URL's. 2) MSVC solutions, if not for all projects, at least for the major ones. 3) An idiots guide to the structure, both physical and logical. I'd like this to work, I really would, the alternative for me is Eclipse! Regards, Dave.
________________________________ From: Mark Hammond [mailto:[EMAIL PROTECTED] On Behalf Of Mark Hammond Sent: 25 November 2008 21:30 To: Dave Cross; python-win32@python.org Subject: RE: [python-win32] Win32Cred build errors I can't recall why we say we need that version - have you tried changing it to see what breaks? Currently the vista SDK needs to be used as some partf of pywin32 are starting to expose things introduced with that OS. Cheers, Mark From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Dave Cross Sent: Wednesday, 26 November 2008 2:29 AM To: python-win32@python.org Subject: [python-win32] Win32Cred build errors Hi all/anybody, Win32credmodule.cpp for pywin32 2.5.212.1 insists on finding a header with #define _WIN32_WINNT 0x501 in it. The WinResrc.h file that comes with Microsoft Platform SDK for Windows Server 2003 R2 is only 0x500 so the build fails. As far as I can see, though, this version of the SDK contains the latest WinCred.h stuff and should work OK. Is this a genuine dependency or a typo? If 501 is required, which SDK(s) support it? Regards, Dave. ************************************************************************ ******** Please consider the environment - do you really need to print this email? This email is intended only for the person(s) named above and may contain private and confidential information. If it has come to you in error, please destroy and permanently delete any copy in your possession and contact us on +44 (0) 161 480 4420. The information in this email is copyright (c) CDL Group Holdings Limited. We cannot accept any liability for any loss or damage sustained as a result of software viruses. It is your responsibility to carry out such virus checking as is necessary before opening any attachment. Cheshire Datasystems Limited uses software which automatically screens incoming emails for inappropriate content and attachments. If the software identifies such content or attachment, the email will be forwarded to our Technology Department for checking. You should be aware that any email which you send to Cheshire Datasystems Limited is subject to this procedure. Cheshire Datasystems Limited, Strata House, Kings Reach Road, Stockport SK4 2HD Registered in England and Wales with Company Number 3991057 VAT registration : 727 1188 33 ************************************************************************ ******
_______________________________________________ python-win32 mailing list python-win32@python.org http://mail.python.org/mailman/listinfo/python-win32
