Georgios Petasis wrote:
>  I have the impression that the included libjvm.dll.a didn't work in my 
>  case (mingw - ActiveTcl), and I created
>  my own. This is why I wanted to know how the file in the original 
>  distribution was built (and if the procedure
>  I followed to re-create it was wrong :-))

See:

http://www.inonit.com/cygwin/jni/invocationApi/archive.html

> >  You will likely
> > run into issues trying to run a tclblend.dll with the Active State 
> > binary as this is not a supported
> > configuration. The tclblend.dll you build needs to be run with the Tcl 
> > release it was compiled against.
> >   
>  If I only stick into creating a JVM from Tcl (and never do the 
>  opposite - load Tcl from Java)
>  will I still have problems? ( I am using a tclblend version that uses 
>  stubs :-) with ActiveTcl/JDK 5)
It does not matter. What you need to do is load the Tcl Blend dll into 
the version of Tcl that it was compiled
agains. Otherwise, you may run into issues. The Tcl Blend configure 
script checks for these kinds of problems
to keep you from making mistakes. If the ActiveTcl binary is compiled 
without threads, then you
will run into crashes sooner or later. Mixing and matching binaries with 
Tcl Blend is not a good idea, you
should use Tcl Blend with the version of Tcl it was compiled for.

Mo


-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
tcljava-dev mailing list
tcljava-dev@[...].net
https://lists.sourceforge.net/lists/listinfo/tcljava-dev