> tclblend.dll would not be that problematic, I could for sure find a way to bring it in the user's file system. Actually, I did not wrap it during my test - it was in my file system and the PATH extended to include it's base directory.
> The problem is obviously the static build of Tcl in Tclkit. It seems that Jvm can not work with the running Tcl_Interp because it does not come from a shared library (tcl.dll). But I don't know that exactly...
>
Ack - it works.
I have scattered several installations of Tclblend in several Tcl installations (ActiveTcl, Msys/Tcl, Tclkit...) and the .dll was loaded from the wrong location. The message is, that Tcl as well as JVM need to load the *same* dll at the same time.
To make it work with Tclkit, Tclblend has to be compiled and linked against stubs, of course. Then, tclblend.dll can not be wrapped, it has to be in the user's file system. So it is best to extract it from the deployed starkit to some location, extend env(PATH) to this location and make sure it is loaded from there rather than from the wrapped extension during "package re java". And - of course jre/bin and jre/bin/client must be on env(PATH).
Pretty cool, still no need for a Tcl installation on the user's machine :-)
Eckhard
_______________________________________________________________
SMS schreiben mit WEB.DE FreeMail - einfach, schnell und
kostenguenstig. Jetzt gleich testen! http://f.web.de/?mc=021192
|