[[... explain meaning ...]]






























[[Discussions in pages on "[VFS]", "[CriTcl builds C extensions on-the-fly]",
"[MicroTcl for Tcl9]", "[Jean-Claude Wippler]",
"[James Garrison]",
"[Script to merge C source files]",
"[How can I compile Tcl type scripts into binary code]",
"[COMPANY: Career Demon.com plc]",
...]]




----
[Bob Techentin] wisely observes, "You might consider a 'traditional' tcl/tk installation, complete [[with]]
additional packages, as a component of your application.  Take a close
look at how [TclPro] tools get installed, and you'll see that the '[wish]'
executable is actually a short shell script which sets some environment
variables (e.g., LD_LIBRARY_PATH) and then execs the binary shell."
----
Another option is to use [TclKit]'s "[scripted document]s" [http://www.equi4.com/scripdoc/].  In a few steps:
   * get TclKit for your platform
   * get the "SDX" scripted doc utility (platform independent) from [http://www.equi4.com/pub/tk/examples/]
   * create dirs "myapp.vfs/", "myapp.vfs/bin/", and "myapp.vfs/lib/"
   * copy your main script to "myapp.vfs/bin/main.tcl"
   * copy all packages you need as dirs inside "myapp.vfs/lib/"
   * wrap it all up using "sdx fs2sd myapp" ("file system to scripted doc")
   * that's it, you have a runnable "myapp"
   * try it (double-click, or run "./myapp" on Unix)
There are ways to make "main.tcl" work in unpackaged as well as in packaged form, which is useful for debugging.  All of this is based on Tcl's Virtual File System or [VFS] in short.  All examples here [http://www.equi4.com/pub/tk/examples/] and here [http://www.equi4.com/pub/dok/] use this same approach, you can unpack them (with "sdx sd2fs ...") to see how they work.  - [JCW]