➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author tlesher
Recipients belopolsky, brett.cannon, doko, georg.brandl, loewis, mark.dickinson, pitrou, rhettinger, rnk, tim.golden, tim.peters, tlesher, vstinner
Date 2010-07-21.19:58:22
SpamBayes Score 0.16829027
Marked as misclassified No
Message-id <1279742304.81.0.564712761354.issue9012@psf.upfronthosting.co.za>
In-reply-to
Content 
No, there's no automated way to keep "legacy" Windows toolchains in sync; short of adopting something like Scons or CMAKE (which I'm *not* suggesting) I don't think I've seen a trustworthy way of doing so.

The PCBuild's "readme.txt" states:

"You can find build directories for older versions of Visual Studio and Visual C++ in the PC directory. The legacy build directories are no longer actively maintained and may not work out of the box."

To date, I believe that the attitude toward these older build files has been "unsupported; use at own risk; patches welcome".
History
Date User Action Args
2010-07-21 19:58:24tleshersetrecipients: + tlesher, tim.peters, loewis, brett.cannon, georg.brandl, rhettinger, doko, mark.dickinson, belopolsky, pitrou, vstinner, tim.golden, rnk
2010-07-21 19:58:24tleshersetmessageid: <1279742304.81.0.564712761354.issue9012@psf.upfronthosting.co.za>
2010-07-21 19:58:23tlesherlinkissue9012 messages
2010-07-21 19:58:22tleshercreate