WiTS (wits.magicsplat.com) is distributed as a starpack including
twapi so that's an existence proof.
/Ashok
On Jun 19, 8:13 pm, "getshor...@gmail.com" <getshor...@gmail.com>
wrote:
> > Thx- Nascondi testo citato
>
> - Mostra testo citato -
You still did not answer what version of Tcl or what version of twapi.
I'll assume the latest released versions of each - Tcl 8.5 and Twapi
2.0.12.
If that's the case, download twapi-2.0.12.tm from the twapi
sourceforge site and stick it into the lib directory under your
WHATEVER.vfs.
That's all that should be needed, I believe, for the package require
to work, or at least that is sufficient for wits. If that does not
work, try directly sourcing the tm from your main.tcl.
If you are using some other Tcl and Twapi versions, please specify
which ones.
/Ashok
This does not exactly agree with my setup, which works. I've used
several versions of each with no problems. Currently I'm using tcl/tk
8.6b1 and twapi 2.0b11
In my vfs/lib/ directory there is a DIRECTORY
vfs/lib/twapi-2.0b11
and inside this directory there's a pkgIndex.tcl, a twapi.dll, and
some 30 other .tcl files.
The app-xxx directory with my startup script is also in the lib
directory.
But the twapi.dll does NOT reside directly in the lib directory.
That's the other (older) way to do it (and the only way for Tcl
versions before 8.5). Loading the tm module from a starkit/starpack is
significantly faster. Windows will open the star* for each file read
from the VFS, and for every open, it will do ACL checks for all parent
directories all the way to the top which adds significant cost to the
startup time if you somewhere under program files. Having a single
file in the starpack reduced startup for wits from 4-5 seconds to
under a second.
/Ashok
> /Ashok- Nascondi testo citato