Hi. I hope this is a simple question. I installed ActiveTcl using the Windows msi (ActiveTcl-8.6.11.1.0000-MSWin32-x64-7d1e110a.msi). The installation seemed to work, but in the ActiveTcl\lib\tclConfig.sh file there are 6 instances of variables that are not well defined. Instead. they have text something like:
variable='C:\TEMP\ActiveState----------------------------------------please-run-the-install-script----------------------------------------"
Okay… so where is the install script? Has the installation not been configured properly? Having these variables ill defined creates problems with compiling other systems (Tcl package for Perl, for example). Or… is it possible that there is no Windows installer script, and that I have to figure out how to edit these variables manually?
Thanks in advance for the help.
Never mind. I was able to edit the configuration file manually and got it to work so that I could compile the Tcl module for Perl. Still, it would be wise for ActiveState to modify their scripts for ActiveTcl for Windows so that these variables are properly set in the future.
Those are supposed to be set as part of the relocation script that the MSI installer runs. Will look into that to see what’s going on there.
Is this issue likely to be addressed? A colleague and I separately had the same problem and had to manually edit the config file. I don’t think our end users would easily be able to do that. We are also attempting to use the Tcl package for Perl which is not possible without the manual edit.
Thanks
We have the issue tracked, so it will get looked at, but I’m not sure which sprint it will get scheduled.
1 Like
I’m trying to sort through this as we speak. I already tried to manually link all the files within the config file but to no avail.
Could someone please point me in the right direction?
TCL keeps failing its install when I try to install the TK package from cpan so the small codebase I’m working with won’t compile. For what it’s worth, I know that the .msi ActiveState installer ran the ‘Complete’ setup and ‘tclsh’ is indeed recognized from my env variables.
The Tk package from CPAN is not related to “tclsh” (or Wish).
Perl’s Tk package as found on CPAN is a re-implementation of Tcl/Tk 8.3 (the language) so that users could write more “Perl-ish” Perl code when they built GUIs instead of needing to learn Tcl/Tk syntax. Since then, Perl Tk has essentially become a “language-within-a-language”.
Tclsh would be from Tcl/Tk (the language). Does your small codebase load a “tclsh” Tcl/Tk interpreter or a “perl” Perl interpreter before it runs the scripts? That will point you to the write kind of project you’ll need.