RetroSearch Browse

Mon Mar 13 00:20:12 CET 2006 · http://mail.python.org/pipermail/python-dev/2006-March/062313.html

[Tim Peters wrote]
> Setup is hellish

Any objections to:

    Index: Tools/buildbot/build.bat
    ===================================================================
    --- build.bat   (revision 42982)
    +++ build.bat   (working copy)
    @@ -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

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.

On one mahcine I was trying this on I didn't have Perl installed to
C:\Perl but to C:\Perl58. People who install to an alternate drive might
also get surprised.

Trent

-- 
Trent Mick
TrentM at ActiveState.com

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from http://mail.python.org/pipermail/python-dev/2006-March/062313.html below:

[Python-Dev] Still looking for volunteer to run Windows buildbot