in reply to Re^2: Link Tcl to a different tcl.dll on Windows
in thread Link Tcl to a different tcl.dll on Windows

I do not want to reinstall Tcl.pm. This of course would work fine. What I want is the ability to link, possibly at runtime, to a Tcl installation of my choice which is present on my computer. And this independently of the Tcl installation I pointed Tcl.pm to at the moment of its installation. See my update for the best solution I managed to get so far.

The simplest way to ensure the two are compatible is to test/build from start -- figure out what works when its supposed to work 100%

  • Comment on Re^3: Link Tcl to a different tcl.dll on Windows

Replies are listed 'Best First'.
Re^4: Link Tcl to a different tcl.dll on Windows
by Takamoto (Monk) on Jan 25, 2020 at 09:33 UTC

    Yes, this is the simplest way, but not the way I want/need to go. Simple like that. Possible scenario: I want to run the same script against two different Tcl installations. I cannot install Tcl.pm anytime I want to switch installation.

      I cannot install Tcl.pm anytime I want to switch installation

      huh? You install once and choose at runtime

      use lib '/activetcltcl86';

      use lib '/activetcltcl85';

      use lib '/bitbuckettcl85';

      use lib '/bitbuckettcl86';