in reply to Re^3: making tcl.pm and Tcl movable
in thread making tcl.pm and Tcl movable
Actually the task is very simple: my department needs to deploy on 50+ macOS laptops a script that needs to call Tcl. This script needs to run in a nutshell, with its own Perl and Tcl version (I know that both are already present on any macOS, but not the desired versions). They do not want to install on all machines Tcl, tcl.pm, and Perl. My task: pack the Perl script + Perl into an executable (which I can do with zero problems with PAR or pp). My problem is to link the script/executable to the Tcl version I will put together with the executable, all packed in a zip file, on the target machines. In the target computer: unpack the zip and run the executable. Inside the zip file:
The problems I have is to link to these Tcl binaries.
No matter what I try, the executable in the target machines is always linked to the standard Tcl distribution, not the one inside the zip). I tried to install tcl.pm against my Tcl binaries. It works, but as soon as I 'move' around my folder with executable+Tcl, it stops to work, since Tcl is no more in sight of the module. I tried with the ENV variable, as pointed out above and in some forum about Tkx, but could not reach any success. Any suggestion would be very much appreciated.
|
|---|
| Replies are listed 'Best First'. | |
|---|---|
|
Re^5: making tcl.pm and Tcl movable
by swl (Prior) on Nov 18, 2018 at 22:32 UTC | |
|
Re^5: making tcl.pm and Tcl movable
by LanX (Saint) on Nov 18, 2018 at 22:22 UTC | |
by Anonymous Monk on Nov 19, 2018 at 23:54 UTC | |
by Anonymous Monk on Nov 19, 2018 at 23:56 UTC |