Specialized Tools Directory Not Being Seen By NANT

13 views
Skip to first unread message

John Laurence Poole

unread,
Aug 9, 2019, 12:13:33 PM8/9/19
to TortoiseSVN
My specially staged Tools directory is not getting picked up by the build scripts.
I am assuming for purposes of NANT that forward slashes, "/", as directory delimiters will be interpreted correctly in Windows as backslash, "\".


I have checked out http://svn.osdn.net/svnroot/tortoisesvn/tags/version-1.12.2
and staged same to: D:\work\TortoiseSVN\version-1.12.2

Per instruction in build.txt (v. 28553, 9:18:48 AM, Thursday, April 11, 2019) lines 60-63:

    - Make a copy of the file default.build.user.tmpl in the TortoiseSVN root folder and
      rename that copy to default.build.user. Then adjust the paths as mentioned
      in that file. You may leave it unchanged if you installed / copied everything
      into the suggested default paths.

I created my build.user file, here's a diff:

    --- D:/work/TortoiseSVN/version-1.12.2/default.build.user.tmpl    Thu Aug 08 15:27:45 2019
    +++ D:/work/TortoiseSVN/version-1.12.2/default.build.user    Thu Aug 08 18:17:12 2019
    @@ -79,7 +79,8 @@
               TODO: change path value, if neither TSVNTOOLS is defined
               nor have tools be copied directly below the TSVN root.
             -->
    -        <variable name="TSVNTOOLS" value="D:\Development\SVN\TortoiseSVN\Tools" />
    +        <!-- jlpoole modified below -->
    +        <variable name="TSVNTOOLS" value="D:\work\TortoiseSVN\Tools" />
           </setenv>
         </if>

    
I had downloaded and unzipped the Tools-1.8.0.zip into D:\work\TortoiseSVN\Tools

Per instruction in build.txt lines line 64 - 67:

     - Make a copy of the file doc\doc.build.user.tmpl and rename that copy to
      doc\doc.build.user. Then adjust the paths in that file according to your
      setup. You need to edit this file if your installed version of Tortoise has a different
      working-copy database version than the tool expects.


I created my doc.build.user file, here's a diff:

    --- D:/work/TortoiseSVN/version-1.12.2/doc/doc.build.user.tmpl    Thu Aug 08 15:27:27 2019
    +++ D:/work/TortoiseSVN/version-1.12.2/doc/doc.build.user    Thu Aug 08 18:17:17 2019
    @@ -10,7 +10,8 @@
       <!-- select the output format of the docs (chm, pdf, html, htmlsingle) -->
       <property name="docformats" value="chm" />
       <!-- select the languages of the docs -->
    -  <property name="languages" value="en,de" />
    +  <!-- 8/8/19 jlpoole: edited below -->
    +  <property name="languages" value="en" />
    
    
       <!-- if you want to use the spellchecker, enable it here -->
    @@ -21,19 +22,19 @@
       <!-- if you've put the 'Tools' folder not below the TortoiseSVN source
       root, you must set the paths here! -->
       <property name="path.bin"
    -    value="${path::get-full-path('c:/Tools')}"
    +    value="${path::get-full-path('D:/work/TortoiseSVN/Tools')}"
         unless="${property::exists('path.bin')}"
       />
       <property name="path.fop"
    -    value="${path::get-full-path('c:/Tools/fop')}"
    +    value="${path::get-full-path('D:/work/TortoiseSVN/Tools/fop')}"
         unless="${property::exists('path.fop')}"
       />
       <property name="path.xsl"
    -    value="${string::replace(path::get-full-path('c:/Tools/xsl'), '\', '/')}"
    +    value="${string::replace(path::get-full-path('D:/work/TortoiseSVN/Tools/xsl'), '\', '/')}"
         unless="${property::exists('path.xsl')}"
       />
       <property name="path.gettext"
    -    value="${path::get-full-path('c:/Tools')}"
    +    value="${path::get-full-path('D:/work/TortoiseSVN/Tools')}"
         unless="${property::exists('path.gettext')}"
       />

 
 
I launch the x86 NationTools Command Prompt for VS 2019 by:
Start -> All Progrmas -> Visual Studio 2019 -> Visual Studio Tools -> VC -> x64_x86 Cross Tools Command Prompt for VS 2019
[%comspec% /k "C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\VC\Auxiliary\Build\vcvarsamd64_x86.bat"]

    **********************************************************************
    ** Visual Studio 2019 Developer Command Prompt v16.2.1
    ** Copyright (c) 2019 Microsoft Corporation
    **********************************************************************
    [vcvarsall.bat] Environment initialized for: 'x86'

    C:\Program Files (x86)\Microsoft Visual Studio\2019\Community>D:

    D:\>cd D:\work\TortoiseSVN\version-1.12.2

    D:\work\TortoiseSVN\version-1.12.2>set PATH=F:\Downloads\SourceForge\Nant\nant-0
    .92\bin;%PATH%

    D:\work\TortoiseSVN\version-1.12.2>set PATH=C:\Python27;%PATH%

    D:\work\TortoiseSVN\version-1.12.2>set TSVNTOOLS=D:\work\TortoiseSVN\Tools

    D:\work\TortoiseSVN\version-1.12.2>nant init
    NAnt 0.92 (Build 0.92.4543.0; release; 6/9/2012)
    Copyright (C) 2001-2012 Gerry Shaw
    http://nant.sourceforge.net

    Buildfile: file:///D:/work/TortoiseSVN/version-1.12.2/default.build
    Target framework: Microsoft .NET Framework 4.0
    Target(s) specified: init


    VSNET:


    env:


    init:


    BUILD FAILED

    D:\work\TortoiseSVN\version-1.12.2\default.build(561,8):
    Unable to download 'https://downloads.sourceforge.net/project/tortoisesvn/build%
    20tools/Tools-1.8.0.zip' to 'D:\work\TortoiseSVN\version-1.12.2\tools.zip'.
        The request was aborted: Could not create SSL/TLS secure channel.

    Total time: 1 seconds.


    D:\work\TortoiseSVN\version-1.12.2>

  
What should happen is that my staged Tools directory is discovered and there is no attempt to download the tool.zip from sourceforge.
Have I missed some setting?  (I'm not addressing the real reason the error was thrown: Could not create SSL/TLS secure channel.
I just wanted to avoid the download step and inserting the Tools into the source controlled tree I had staged.

John Laurence Poole

unread,
Aug 9, 2019, 12:15:39 PM8/9/19
to TortoiseSVN
Also, I worked around this by copying my Tools directory and placing it under D:\work\TortoiseSVN\version-1.12.2 so I could move forward.

turnin...@outlook.de

unread,
Jan 30, 2020, 5:06:57 PM1/30/20
to TortoiseSVN
Maybe it does not help but I did post an issue to nant Github about this: https://github.com/nant/nant/issues/178 

Reply all
Reply to author
Forward
0 new messages