From: Trent Mick <trentm@activestate.com>
Date: Sun, 12 Mar 2006 23:40:58 +0000 (+0000)
Subject: Adding the /useenv means that one's PATH actually gets through. This is
X-Git-Tag: v2.5a0~269
X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=b1386772b5864f18bde618f76f4291986a48ed8c;p=python

Adding the /useenv means that one's PATH actually gets through. This is
important for the _ssl.vproj build. It calls build_ssl.py which tries to
find a Perl to use. Without "/useenv" Visual Studio is getting a PATH
from somewhere else (presumably from its internal environment
configuration). The result is that build_ssl.py fallsback to its
"well-known" locations for a Perl install.
---

diff --git a/Tools/buildbot/build.bat b/Tools/buildbot/build.bat
index aa019a9c78..00bbdbb72b 100644
--- a/Tools/buildbot/build.bat
+++ b/Tools/buildbot/build.bat
@@ -1,3 +1,3 @@
 @rem Used by the buildbot "compile" step.
 call "%VS71COMNTOOLS%vsvars32.bat"
-devenv.com /build Debug PCbuild\pcbuild.sln
+devenv.com /useenv /build Debug PCbuild\pcbuild.sln