making tcl.pm and Tcl movable

Anonymous Monk has asked for the wisdom of the Perl Monks concerning the following question:

I have been asked to install tcl.pm in order to be hard linked to a specific installation so that everything can be moved without tcl.pm loosing sight of Tcl. Linking to a specific Tcl installation is easily achievable by using: perl Makefile.PL --tclconfig /opt/local/lib/tclConfig.sh as pointed out in several forums. However, this doesn't make it 'movable'. I do not think it is possible to install tcl.pm to make it 'movable', even if in the POD the author seems to indicate this. I guess I should work with some ENV variables, for example like in tkx.pm using something like $ENV{'PERL_TCL_DL_PATH'} = $frameworkpath;, for example at BEGIN time. But some mechanism like this seems not to exist in tcl.pm. Any ideas that I could explore?

Flo.

Comment on making tcl.pm and Tcl movable Select or Download Code

Replies are listed 'Best First'.
Re: making tcl.pm and Tcl movable by LanX (Saint) on Nov 17, 2018 at 17:26 UTC
Sorry I have problems to understand what you mean with "movable" Moving to other directory on same filesystem or other host? It would certainly help to reproduce your problem. Cheers Rolf _{(addicted to the Perl Programming Language :) Wikisyntax for the Monastery FootballPerl is like chess, only without the dice}	[reply]
Re^2: making tcl.pm and Tcl movable by Anonymous Monk on Nov 17, 2018 at 18:05 UTC
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).	[reply]
Re^3: making tcl.pm and Tcl movable by LanX (Saint) on Nov 17, 2018 at 20:07 UTC
My Par, TK and Mac foo is limited, so I will not be able to help you, sorry ... > the description I have ... I guess Perl and tcl.pm will ... they will pack ... but what I can say is that your description is very vague cause it seems you don't even know what your client exactly wants and does. (It sounds almost like you are trying to apply to a job offer from the internet. ;-) A reproducible problem description would greatly increase the probability to get help here. HTH! Cheers Rolf _{(addicted to the Perl Programming Language :) Wikisyntax for the Monastery FootballPerl is like chess, only without the dice}	[reply]
Re^4: making tcl.pm and Tcl movable by Anonymous Monk on Nov 18, 2018 at 21:54 UTC
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
Some notes below your chosen depth have not been shown here
Re^3: making tcl.pm and Tcl movable by Anonymous Monk on Nov 17, 2018 at 20:23 UTC
Tkx depends directly on tcl.pm	[reply]