Re: [Ikvm-developers] OpenJDK version corresponding to IKVM's internal Java class library

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

Hi,


a)       Since IKVM 7 the major version matches the major Java version. Java is generally very good at backward compatibility, so you should be able to convert and run 1.5 jars with IKVM 8 just fine.

b)      Except for IKVM.OpenJDK.Tools.dll, all IKVM.OpenJDK.*.dll files are on the boot classpath.

c)       There are some missing parts in the class library (not the language). If you try to use them, you'll probably get some exception. There are also parts that are implemented but not "supported" (i.e. if you find a bug there is no guarantee I'll try to fix it).

I hope this helps.

Regards,
Jeroen

From: Richard Callahan [mailto:ri...@lu...]
Sent: Tuesday, November 3, 2015 15:11
To: ikv...@li...
Subject: [Ikvm-developers] OpenJDK version corresponding to IKVM's internal Java class library

Hi,

Here's my second question (of three) today. First, thanks again to Mr. Frijters for a great tool!! Back in August I posted a bug report, and in responding to it<http://sourceforge.net/p/ikvm/bugs/303/#6b08> Mr. Frijters pointed out that it's unwise to attempt to compile a JAR file that's part of the JDK and reference it as a dependency, because as he puts it, "IKVM comes with its own Java class library and you can't mix in another one." I just wanted to follow up about that, because I'm very much a newbie with respect to understanding what is going on under the hood of IKVM.

Searching the forums for other posts concerning this topic hasn't uncovered much for me, but I did take a look at the internals of some of the DLL files in the /bin directory of ikvm-7.2.4630.5, and it looks like indeed many classes from OpenJDK are there in the form of DLL files. This question has two small parts to make sure I understand this correctly:


a)       I can't tell, by opening up these DLL files, what version of OpenJDK they were compiled from. Does the major version number for IKVM match to the version of OpenJDK that it uses? (So IKVM 8 uses OpenJDK 8, IKVM 5 uses the OpenJDK associated with Java 1.5, etc.?) If so, does that mean that if I want to convert a Java application that has its compliance level set to 1.5 in Eclipse to a DLL file while referencing JDK classes, I have to use IKVM 5 for the conversion? Or can I use a later version of IKVM? (I know I have to use IKVM 8 to convert JAR libraries compiled using Java 1.8.)

b)      I'm assuming that the files in IKVM's /bin directory are on IKVM's class path when IKVMC is converting JAR files to DLL files. Does that mean that any class that's in a library file that is part of the Open JDK internal JAR libraries is part of this directory? If not, how do I know what's already on the IKVM classpath and what JDK JAR file I have to attempt to convert to a DLL file before referencing it?

c)       I saw in the limitations page<http://sourceforge.net/p/ikvm/wiki/Limits/> for this project that there are some Java language features that IKVM currently does not support. This might be naïve for me to ask, but what happens if I try to take one of those features contained in an OpenJDK JAR library, convert the JAR file to a DLL file, and reference it as a dependency in a call to IKVMC? Would something crash and burn or is that feasible? (Something tells me this is a newbie question, or that would be recommended in the FAQ.)

If the answer to some of this is "look at some comments in the source code," that's fair and perhaps a pointer to the right section might help the forum readers. Thanks again for such a great piece of software!

Best,

Richard