I tried using Tcl.pm with Magicsplat. Because Magicsplat's tclsh did not provide a tclConfig.sh to Tcl.pm's installation script, Tcl.pm could not locate the Tcl DLL file (tcl86t.dll). I am wondering if Magicsplat could provide a tclConfig.sh?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I've logged a ticket for this as a reminder for the next release although I'm not sure how useful it would be. The magicsplat distro is based on the nmake builds in the Tcl repository. The tclconfig.sh that gets built does not actually reflect the compilation accurately with nmake builds as opposed to the autoconf builds. However, it might be accurate enough for your purposes. Do you happen to know which particular setting you need? Just TCL_DLL_FILE or something else as well?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi Ashok, thanks for releasing 1.9.1. I've finally given it a try. TCL_DLL_FILE specifying just the name is correct as far as I know.
However I now notice that Tcl.pm will make more extensive use of the other variables in tclConfig.sh if they're present. But the paths that many of them used still contain the path from the build machine (D:\src\tcl-installer\win\dist\x64), and are not updated by the installer to reflect where they actually are on my system. Ideally, variables like
TCL_PREFIX='D:\src\tcl-installer\win\dist\x64'
should get updated to instead say
TCL_PREFIX='C:\Program Files\Tcl86'
or whatever the installation path was.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Additionally, tclConfig.sh specifies variables for source directories (D:\src\tcl-installer\sources\tcl) not in the distribution. Should those ideally be removed by the installer?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anonymous
Anonymous
-
2019-05-24
I'll take a look next time I make a release. Do you know which specific variables are used?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I tried using Tcl.pm with Magicsplat. Because Magicsplat's tclsh did not provide a tclConfig.sh to Tcl.pm's installation script, Tcl.pm could not locate the Tcl DLL file (tcl86t.dll). I am wondering if Magicsplat could provide a tclConfig.sh?
I've logged a ticket for this as a reminder for the next release although I'm not sure how useful it would be. The magicsplat distro is based on the nmake builds in the Tcl repository. The tclconfig.sh that gets built does not actually reflect the compilation accurately with nmake builds as opposed to the autoconf builds. However, it might be accurate enough for your purposes. Do you happen to know which particular setting you need? Just TCL_DLL_FILE or something else as well?
Yes, TCL_DLL_FILE should be enough to get it working.
I've released 1.9.1 of the magicsplat distribution. Please check if it meets your needs in terms of both tkconfig.sh as well as Tix.
As an aside note that TCL_DLL_FILE only notes the DLL name not the path, I don't know if that suffices for you
Hi Ashok, thanks for releasing 1.9.1. I've finally given it a try.
TCL_DLL_FILEspecifying just the name is correct as far as I know.However I now notice that Tcl.pm will make more extensive use of the other variables in tclConfig.sh if they're present. But the paths that many of them used still contain the path from the build machine (D:\src\tcl-installer\win\dist\x64), and are not updated by the installer to reflect where they actually are on my system. Ideally, variables like
should get updated to instead say
or whatever the installation path was.
Additionally, tclConfig.sh specifies variables for source directories (D:\src\tcl-installer\sources\tcl) not in the distribution. Should those ideally be removed by the installer?
I'll take a look next time I make a release. Do you know which specific variables are used?