IKVM Discussion

[fahadsuhaib]

Hi,

This works really cool, I tried out the samples with the iText one and it worked fine. Some questions relating to this,

1) I see IKVM has wrapper DLLs that we need to use to interact with Java core libraries

• Is this really necessary? Can't we just do a <...core.jar> n use IKVM to create the stub classes and see how it works? Assuming IKVM itself generated those dlls by the same logic 2) I tried doing the above with rt.jar, and IKVM dint expose the functionality much, there was a slight correction to be made to get the compilation work with long folder strings,

let private getIKVMArgs outputPath (jarFile : string) = 
    let outDll = Path.Combine(outputPath, getAssemblyName jarFile)
    outDll, sprintf "-target:library -out:\"%s\" \"%s\"" outDll jarFile

Any idea why so? I haven't worked much with Java more like a noob in that :), but would certainly want to use this super TypeProvider for doing cool stuff.

Thanks, Fahad

[fahadsuhaib]

BTW, rt.jar is found in the jre\lib folder in the Java installation,

[colinbull]

Sorry about the delay in replying, real work swamped me.

Just out of curiosity did your folder path have spaces in it for example C:\Program Files... ? That is probably why you needed to change that. I'll make the changes above.

As for the those dll's I have been playing with how references work in type providers, I think I can get it to transparently reference the OpenJDK libs. If not I'll look at what you suggested however I think that things like classpaths and the way java resolves libs may get in the way with this approach.

Cheers

Colin