Menu ▾ ▴

#5 Installation problems under Windows

None
closed
Simon Wright
Documentation (3)
5
2020-01-30
2011-09-17
Simon Wright
No

TASH doesn't set up at all easily with Windows; you can bend it into shape, but it's a continual challenge.
For starters, Cygwin's Tcl/Tk doesn't play with GNAT (which on Windows is a Windows application, in spite of referencing mingw32). As an example, you can't open the right gnatls; if you can open it at all, it picks up the Cygwin one regardless of the PATH setting.
So you install ActiveState's Tcl; this doesn't know about Cygwin's paths, so setup fails (and if you overcome that one, see below, there are problems in test: 'sort' picks up the Windows version, which isn't case sensitive, causing a test failure).
To install under Windows, (a) do the setup by double-clicking on setup.tcl, (b) ensure in Cygwin that /cygdrive/c/Tcl/bin and /cygdrive/c/GNAT/2011/bin are first in your PATH.

Discussion

  • Alex Proudfoot

    Alex Proudfoot - 2013-06-14

    The Freq tests fail for me. See attached log. In what ways could this cause problems in general operation? Or am I good to go?

     

    Last edit: Alex Proudfoot 2013-06-14
    test.log

    • Simon Wright

      Simon Wright - 2013-06-15

      This is what I meant by 'sort' picks up the Windows version, which isn't case sensitive, causing a test failure.

      Here, (Windows XP and Cygwin 1.7.9(0.237/5/3) 2011-03-29 10:10 i686), and I think on your setup too since the Perl log shows a failure in the very first line of output, freq.pl also fails because Cygwin's perl doesn't strip off the \r in the Windows \r\n. Not that I care a lot about Perl, I guess it was to prove a point about the speed.

      Personally I've always thought the best reason for using TASH is to allow a Tcl interface to an Ada program; especially since Ada2005, why bother to use imported Tcl facilities in Ada? Of course, you'd only need a tiny subset of TASH to do that, and TASH is what it is.

      This feature of the Windows implementation isn't likely to cause you a lot of bother; the problem is that when the ActiveTcl interpreter sees a command it doesn't recognise it tries to execute it in a CMD shell. I can't immediately see how to fix this!

       

  • Simon Wright

    Simon Wright - 2020-01-30
    • status: open --> closed
    • Group: --> None
     

  • Simon Wright

    Simon Wright - 2020-01-30

    Installation instructions cover this now.

     

Anonymous
Anonymous

Add attachments
Cancel