tcl/tk compiler

[Roger Oberholtzer]

Tcl/Tk apps require more than your own stuff. An installer/wrapper puts
all you need into a single installable binary so that the user need not
be concerned with these details. If your parts are compiled is fine. But
this is not really needed. Most people who want such compilers want to
hide what their program does. Being an interpreted language means your
source is available to the user. Compiling hides the source.

I have now remembered the two items:

	freewrap (http://freewrap.sourceforge.net)

and

	InstallBase (http://freewrap.sourceforge.net)

They are both very popular for making packages. Especially freewrap. I
think InstalBase is a meta-freewrap.(built on top of freewrap).


On Fri, 2003-12-26 at 03:10, Ken Moffat wrote:
> Roger Oberholtzer wrote:
> 
> >The compiler is a byte-code compiler. Mainly meant for speed. However,
> >one benefit of the Sun days with Tcl was a JIT compiler. 
> >
> 
> This one, mentioned earlier, won't do what you need?
> 
> http://www.icemcfd.com/tcl/ice.html
> 
> quote:
> Using the ICE Tcl Compiler, you can take advantage of all of these 
> [tk/tcl] features, and also obtain significantly higher performance, the 
> ability to distribute your Tcl/Tk-based applications as compiled code 
> rather than in source form, and the convenience of having the most 
> popular extensions already integrated and compiled on a variety of 
> platforms.
> 
> The compiler translates Tcl code into C code, which can then be compiled 
> together with a special Tcl library to produce a single executable. 
> Alternatively, on most systems it can be compiled into a dynamically 
> loadable module, which can be loaded and run directly by our custom 
> interpreter.
> 
> 
>