O/H Mo DeJong ??????:
>  Georgios Petasis wrote:
>    
> > Hi all,
> >
> > I tried to build tclblend 1.4.0 under windows with mingw, and there is
> > something I didn't
> > understand during the building process: how is tclblend linked with the
> > jvm.dll.
> >
> > I downloaded the sources, configured and build everything required (i.e.
> > following
> > http://wiki.tcl.tk/9993), abd the build went ok. However, I didn't
> > understood how
> > the library libjvm.dll.a (inside win directory) has been built. It is
> > included in the sources, but I couldn't
> > get it to work under ActiveTcl, untill I re-build it my self.
> >   
> >     
>  The libjvm.dll.a file is used when liking only in the case where the 
>  jvm.lib file that comes with the
>  JDK fails to work. Some jvm.lib files from some vendors don't work with 
>  gcc, so the workaround
>  is needed in those cases. But, once tclblend.dll is linked, this file is 
>  no longer needed.
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 :-))
>   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)

Regards,

George