Closed nico-csp closed 1 year ago
We recommend people simply trying to add a Java library to their .NET application use IkvmReference or MavenReference, as described in the README. The command line options to ikvmc are very long and complicated, and IkvmReference provides them automatically baesd on the build environment.
Otherwise, ikvmc needs a -reference argument for each of the ref assemblies that are part of the target framework; and a -runtime argument pointing to the version of IKVM.Runtime you want the generated assembly to bind to.
Thank you! Understood. I will try that instead then. The message "internal compiler error" sounded like a more general problem.
When adding the JAR via IkvmReference
, it seems to work flawlessly.
So for me, the issue could be closed. Thanks for your support!
Or do you think, the issue should stay open, because "internal compiler error" requires additional treatment in the code?
Our poor error messages already have bugs open.
Symptom
FileNotFoundException
occurred; tool asked to file a ticket.IKVM Version and Package
I used the ZIP package
The Task
I tried to convert a JAR to a DLL by calling
ikvmc
.This was the call and output:
Question
Could there be a simple workaround for the time beeing?