Re: [Ikvm-developers] Modularization

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

Yes, the idea is that you can only deploy that DLLs that you need. However, other than testing there is no way to determine which DLLs you app needs. You can look at the static dependencies using any standard .NET tool that shows them, but any dynamic dependencies (including ones that may be in the OpenJDK DLLs) you'll have to find out through testing.

The -sharedclassloader option is used when you're compiling multiple target assemblies at once and want them to share an assembly class loader. For example:

ikvmc -sharedclassloader { foo.jar } { bar.jar }

This will result in foo.dll and bar.dll and both will have the same classloader. By default each assembly gets its own classloader.

Regards,
Jeroen

________________________________
From: Bryan [deb...@gm...]
Sent: Wednesday, April 29, 2009 9:32 PM
To: ikv...@li...
Subject: [Ikvm-developers] Modularization

With the new modularization of ikvm.openjdk.dll, I assume that I can choose to only deploy DLL's that contain packages I am using, correct?  Is there any mechanism to know which DLL's are needed by my code?  Does an ikvmc switch tell me that?  Also, I'm not entirely clear on what the -sharedclassloader option is supposed to do.

Thanks for any help, and for a great project!

Bryan