Single-file executable with tcom

'Anyone have counsel on a convenient way to generate a single-file
executable with tcom capabilities (and when are we going to start
a COM-for-Tcl mailing list?)?  Neither tclkit nor dqkit build in
tcom, ActiveTcl requires installation, ...  Yes, I see several
alternative approaches; I just wonder which have already proven
successful, without unpleasant surprises.

In article <r1aa42-q3m.ln1@lairds.us>, Cameron Laird <claird@lairds.us> wrote:
>'Anyone have counsel on a convenient way to generate a single-file
>executable with tcom capabilities (and when are we going to start
>a COM-for-Tcl mailing list?)?  Neither tclkit nor dqkit build in
>tcom, ActiveTcl requires installation, ...  Yes, I see several
>alternative approaches; I just wonder which have already proven
>successful, without unpleasant surprises.


I'm not quite sure what you mean by "Neither tclkit nor dqkit build in
tcom...."   I have successfully built a starpack with tcom as a
library, along side my 'sdx wrap'ed application.  I'm
using the precompiled tcom.dll from the tcom distribution.
My vfs looks like (from memory, I'm not at the machine I have the on):

myapp.vfs:
--main.tcl
--lib
--lib/app-myapp/
--lib/app-mayap/pkgIndex.tcl
--lib/app-mayap/myapp.tcl
--lib/tcom/
--lib/tcom/pkgIndex.tcl
--lib/tcom/tcom.dll


then:
sdx wrap myapp -runtime /path/to/tclkit-win32.exe


Does this not work for you?  Per startkit/starpack docs,
the tclkit-win32.exe you specify as -runtime should
be a copy of the tclkit you're running with the sdx command.
--
Tom Poindexter
tpoindex@nyx.net
http://www.nyx.net/~tpoindex/

Cameron Laird wrote:

> 'Anyone have counsel on a convenient way to generate a single-file
> executable with tcom capabilities (and when are we going to start
> a COM-for-Tcl mailing list?)?  Neither tclkit nor dqkit build in
> tcom, ActiveTcl requires installation, ...  Yes, I see several
> alternative approaches; I just wonder which have already proven
> successful, without unpleasant surprises.

Tcom is stubs enabled, just put it in your starpack and load/package
require it -- tclkit will do all of the magic for you.

--
+--------------------------------+---------------------------------------+
| Gerald W. Lester               | "The man who fights for his ideals is |
| Gerald.Lester@cox.net          |  the man who is alive." -- Cervantes  |
+--------------------------------+---------------------------------------+

In article <737310543.651335@irys.nyx.net>,
Tom Poindexter <tpoindex@nyx.net> wrote:
>In article <r1aa42-q3m.ln1@lairds.us>, Cameron Laird <claird@lairds.us> wro
te: 
>
>
>I'm not quite sure what you mean by "Neither tclkit nor dqkit build in
>tcom...."   I have successfully built a starpack with tcom as a
>library, along side my 'sdx wrap'ed application.  I'm
>using the precompiled tcom.dll from the tcom distribution.
>My vfs looks like (from memory, I'm not at the machine I have the on):
>
>myapp.vfs:
>--main.tcl
>--lib
>--lib/app-myapp/
>--lib/app-mayap/pkgIndex.tcl
>--lib/app-mayap/myapp.tcl
>--lib/tcom/
>--lib/tcom/pkgIndex.tcl
>--lib/tcom/tcom.dll
>
>
>then:
>sdx wrap myapp -runtime /path/to/tclkit-win32.exe
>
>
>Does this not work for you?  Per startkit/starpack docs,
>the tclkit-win32.exe you specify as -runtime should
>be a copy of the tclkit you're running with the sdx command.