> 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!

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:

• executable
• Tcl binaries

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.

Is the problem that you need to update your path in the script to include the packed location?

If so then something along the lines of the code below might be sufficient. It assumes the files are packed with the executable, so adjust paths as needed.

BEGIN {
    if ($ENV{PAR_0}) {
        use Config;
        $ENV{PATH} .= "$Config{path_sep}$ENV{PAR_TEMP}";
    }
    #print $ENV{PATH};
};
[download]

Or, if they are in a directory at some arbitrary level above the script's location then something more complex like:

#  not fully tested, not properly adapted to the Tk case,
#  and likely has side effects
BEGIN {
    #  Search up the tree until we find the tk dir that contains a bin
+ folder
    use Path::Class;
    use Config;
    use FindBin qw /$Bin/;

    #say "PAR_PROGNAME: $ENV{PAR_PROGNAME}";
    my $prog_name  = $ENV{PAR_PROGNAME} || $Bin;

    my @paths;
    use Config;
    my $tk_dir  ='tk';

    #  add the tk bin dir to the path
    my $origin_dir = Path::Class::file($prog_name)->dir;

  ORIGIN_DIR:
    while ($origin_dir) {

        my $inner_path = Path::Class::dir($origin_dir, $origin_dir);
        #say "Checking $inner_path";
        my $bin_path = Path::Class::dir($inner_path, 'bin');
        if (-d $bin_path) {
            #say "Adding $bin_path to the path";
            push @paths, $bin_path;
        }

        my $old_dir = $origin_dir;
        $origin_dir = $origin_dir->parent;
        last ORIGIN_DIR if $old_dir eq $origin_dir;
    }

    my $sep = $Config{path_sep};
    $ENV{PATH} = join $sep, @paths, $ENV{PATH};
}
[download]

You could also try pp_simple if it's just the dynamic libs that need to be packed.

Did you dump @INC and $ENV{PATH} to be sure that the path to system TCL comes after bundled TCL?

Cheers Rolf
_{(addicted to the Perl Programming Language :)
Wikisyntax for the Monastery FootballPerl is like chess, only without the dice}