Open Lancelotbronner opened 3 days ago
I'm not sure in your reasoning here. Tons of people use IkvmReference on the newest Macs. I have unit tests. And a Mac.
The dynamic code restrictions are in Catalyst and iOS. Neither of which you build from.
My reasoning was I updated to net8 and the latest IKVM version and now the project always fails at runtime with a message about dynamic code generation being unavailable for the platform.
This is when compiling for macOS arm64 and running in a .NET 8 console app.
My reference was just the Include, nothing else. Is there something I should add? Are there known incompatibilities of IKVM with certain dotnet configurations?
I looked through the docs and couldn't find any counter-indications. Is there up-to-date documentation anywhere?
IKVM uses dynamic code generation at runtime. Nothing to do with whether you statically compile your specific assembly or not. So it does not support AOT.
But it will run as a normal .NET app on OSX just fine.
I'm trying to convert a jar to an assembly and, so far, I'm finding the process very difficult.
I'm doing this because the dynamic
IkvmReference
no longer work as of IKVM 8 on macOS because it uses dynamic code generation which isn't supported.I haven't found any other docs than the ones at https://ikvm.org/ikvm which don't help with the troubleshooting.
I downloaded the latest tools from Github releases.
Here's my command:
And the resulting error: