Re: [tcltk-perl] RE: Tcl-Tk-0.77

[Vadim K. <va...@ar...>]

> > BTW it would be good to develope a feature when Tcl/Tk
> > binaries, that Tcl::Tk use, could live in any directories, so
> > to ease creating of distributions that could be moved and
> > executed without requiring TCL to be installed (it is really
> > easy and I use this at work).
>
> Can you elaborate on what you mean here?  I think I understand
> it to mean relocatable shared libs on any platform, but I'm
> not quite sure.

I was thinking only for Windows, but yes, having such a feature on all
platforms must be done, not only for one of them.

I meant that from time to time it is needed to package all required files
into one executable so to have a possibility to run it regardless whether
computer have Tcl (or Perl) installed.
This is why "starkit"/tclkit is needed, and Perl's PAR.


>
> I've thought about having an optional configuration option for
> Tcl::Tk that uses the stubs libraries.  It is a bit tricky, but
> then it would operate like the Tcl browser plugin.  There
> would be no implicit dependencies on a particular set of Tcl/Tk
> dlls.  Instead you would start up and then try to load the Tcl
> and Tk dlls based on a set of heuristics.  This frees you from
>
> a) implicit dll tiedown
> b) version dependency (can use Tcl 8.5 even if compiled for 8.4)
> c) location dependency (see the npWin.c to see how I allow for
>    several locations)

It would be fine if mentioned "heuristic" could be configured somehow. Most
obviously - to have a way to specify exact location of binaries. Up to now I
used some hack for this.

>
> NpCreateMainInterp:
>
http://cvs.sourceforge.net/viewcvs.py/*checkout*/tclplugin/tclplugin/generic
/
> npInterp.c?content-type=text%2Fplain&rev=1.6
>
> NpLoadLibrary:
>
http://cvs.sourceforge.net/viewcvs.py/*checkout*/tclplugin/tclplugin/win/npW
i
> n.c?content-type=text%2Fplain&rev=1.7
>
> This would go in Tcl.xs:BOOT

Great.

Best regards,
Vadim.