Re: [Ikvm-developers] IKVMC creating assembly with references to wrong OpenJDK runtime

[Jeroen F. <je...@su...>]

Hi Michael,

There's really not much magic going on, so it has to be something relatively simple.

Have you double checked the MyDotNet\ikvm-0.46.0.1\bin\IKVM.OpenJDK.*.dll files to make sure they are the right version?

Personally, I recommend using ILDASM to look at the dependencies (look inside the MANIFEST node), because it is very low level and doesn't do any "clever" stuff.

Regards,
Jeroen

________________________________________
From: Michael Kay [mi...@sa...]
Sent: Monday, December 05, 2011 6:13 PM
To: ikv...@li...
Subject: [Ikvm-developers] IKVMC creating assembly with references to wrong     OpenJDK runtime

Jeroen et al,

I am running IKVMC 0.46.0.1 to convert a JAR file to a .DLL assembly,
and I am ending up with an assembly that contains dependencies on the
0.42.0.3 versions of DLLs such as IKVM.OpenJDK.Core.

This is what I am doing:

MyDotNet\ikvm-0.46.0.1\bin\ikvmc.exe ^
     -out:9.4/temp/n/dll/ee/saxon9ee.dll ^
     -assembly:saxon9ee ^
     -target:library ^
     -keyfile:MyDotNet/saxondotnet.snk ^
     -version:9.4.0.1 ^
     -debug ^
     -reference:mscorlib.dll ^
     -reference:System.Xml.dll ^
     -reference:System.dll ^
     -reference:MyDotNet\ikvm-0.46.0.1\bin\IKVM.OpenJDK.Core.dll ^
     -reference:MyDotNet\ikvm-0.46.0.1\bin\IKVM.OpenJDK.Charsets.dll ^
     -reference:MyDotNet\ikvm-0.46.0.1\bin\IKVM.OpenJDK.Text.dll ^
     -reference:MyDotNet\ikvm-0.46.0.1\bin\IKVM.OpenJDK.Util.dll ^
     -reference:MyDotNet\ikvm-0.46.0.1\bin\IKVM.OpenJDK.XML.API.dll ^
     -srcpath:9.4/temp/n/jsource ^
     9.4/temp/n/jar/saxon9ee.jar 9.4\temp\n\jar\asm*.jar
e:\mon-repos\lib\xerces.jar

I then list the dependencies using a powershell script, which outputs:

Details for 9.4\temp\n\dll\ee\saxon9ee.dll
Full name: saxon9ee, Version=9.4.0.1, Culture=neutral,
PublicKeyToken=e1fdd002d5083fe6
Dependencies:
0.42.0.3       IKVM.OpenJDK.Charsets
0.42.0.3       IKVM.OpenJDK.Core
0.42.0.3       IKVM.OpenJDK.Security
0.42.0.3       IKVM.OpenJDK.Text
0.42.0.3       IKVM.OpenJDK.Util
0.42.0.3       IKVM.OpenJDK.XML.API
0.42.0.3       IKVM.Runtime
2.0.0.0        mscorlib
2.0.0.0        System
2.0.0.0        System.Xml
...........................................

When I use the same script to process a different but very similar JAR
file (saxon9pe.jar) the references are to 0.46.0.1 as expected. The only
significant difference between the two JAR files, as far as I can tell,
is that the problem one (saxon9ee.jar) references additional external
classes.

I have no idea where the references to 0.42.0.3 are being picked up
from. I have done my best to eliminate 0.42.0.3 from my system (for
example, uninstalling it from the GAC) - but clearly without success.

I'm stuck!

Michael Kay
Saxonica

------------------------------------------------------------------------------
All the data continuously generated in your IT infrastructure
contains a definitive record of customers, application performance,
security threats, fraudulent activity, and more. Splunk takes this
data and makes sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-novd2d
_______________________________________________
Ikvm-developers mailing list
Ikv...@li...
https://lists.sourceforge.net/lists/listinfo/ikvm-developers