-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Tim Roberts wrote: > Stephen Warren wrote: >> Ah, so just so I understand - the full version of VC packages the >> platform SDK into the install so that it's automatically available >> without user action? > > Yes, a Platform SDK is installed with the package. It's an older one > (April 2005), so it's not entirely clear that it is a benefit for them > to do so...
OK. So, for the official Python builds, which platform SDK is used? When I edit the docs to note that it's required, I guess I should specify which one to use! Also, my eventual desire is to submit a patch to implement hard-link functionality for Win32 via CreateHardLink. I'm not sure if this kind of thing influences the version of the Platform SDK that's required. I suspect that in order to allow for backwards-compatibility (i.e. Python still runs on e.g. Win95), I should follow the same trick used for other optional API functions, and not statically link against the library/function, but instead acquire the function's address at run-time. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFG+Uz/hk3bo0lNTrURArenAKDnL+wMfqAJBU371CUL35kJ/N86UQCeMBd+ Al8Ko9vg2FT1U6jmxaq2Axc= =Nqhy -----END PGP SIGNATURE----- _______________________________________________ python-win32 mailing list python-win32@python.org http://mail.python.org/mailman/listinfo/python-win32
