From: Larry W. Virden on 18 Feb 2010 07:08 On Feb 17, 6:43 pm, mike...(a)webmail.us wrote: > Thanks. I started with Active State, then switched to a combination > of their docs and tclkit for my runtime, long before posting my > original message. The problem with Active State's distribution is it > doesn't come with a free one-file deployment solution like tclkit, > unless I missed something... > Check out http://wiki.tcl.tk/base-tcl . While I don't see any man page or other references to base-tcl in the activetcl docs, the runtime is present for the hardware/software platforms supported. If you need to support other variations, then you have the choice of other negotiating a contract with ActiveState for support of the platform, or to choose one of the other variations which provide source so that you can build and support the technology yourself.
From: tomk on 18 Feb 2010 15:32
On Feb 17, 4:43 pm, mike...(a)webmail.us wrote: > On Jan 30, 12:42 pm, tomk <krehbiel....(a)gmail.com> wrote: > > > I would recommend that you use the Active State distribution, here is > > the man page for their packageshttp://docs.activestate.com/activetcl/8.5/at.pkg_index.html. > > Thanks. I started with Active State, then switched to a combination > of their docs and tclkit for my runtime, long before posting my > original message. The problem with Active State's distribution is it > doesn't come with a free one-file deployment solution like tclkit, > unless I missed something... Mike, It isn't immediately obvious but a "basekit" in the ActiveState distribution IS a tclkit so you don't need to do any switching. I develop for multiple platforms using the basekits and sdx to do the wrapping (both starkits and starpacks) with out any problem. Tom K. |