the description I have is that they need to ship a perl script to several machines (Mac). The script calls TCL through tcl.pm which is going to be shipped too (I guess Perl and tcl.pm will be packed with PAR or something similar, executable and Tcl in a zip file). Also, they will pack alTcl and need the script to call that precise binary of Tcl and no others.
I have tryed to understand the logic behind tcl.pm, as far as the linking to Tcl is concerned, but without much success. It works out of the box for the local Tcl installation it finds when it is installed, but I fail to twik it completely. Hope it is more clear what I am trying to achieve. With Tkx.pm it seems to be possible to pass at run time the location of Tcl that a Perl script should be used. Tcl.pm doesn't seem to allow the same, nor the hardcoding of a particular location relative to itself (with the goal of having my packed script a Tcl in a directory and move it around, from machine to machine and so on).
In reply to Re^2: making tcl.pm and Tcl movable
by Anonymous Monk
in thread making tcl.pm and Tcl movable
by Anonymous Monk
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |