Awesome!! I will check this out.
That post links to an issue that will hopefully result in formal support for that pathway.
The article about Multi-tier compilation in GraalVM https://medium.com/graalvm/multi-tier-compilation-in-graalvm-5fbc65f92402
Link to https://www.twitch.tv/r/e/eyJjaGFubmVsIjoidGhvbWFzd3VlIiwibG9jYXRpb24iOiJoZWFkZXIiLCJlbWFpbF9pZCI6IjY3M2U2N2E1LTZlOTEtNDU2YS04NGFiLTY1MjAwNjU0Njg1NCIsInNvdXJjZV9lbWFpbCI6InR3aXRjaF9mYXZvcml0ZV91cCIsIm5hbWUiOiJ0d2l0Y2hfZmF2b3JpdGVfdXAiLCJsb2dpbiI6IiJ9/116892570/ff2fa62161767e2e1df563684d8d65d6b5415d22/thomaswue?ignore_query=true&tt_content=twitch_favorite_up&tt_email_id=673e67a5-6e91-456a-84ab-652006546854&tt_medium=email with discussion
Thanks. This is JNI specific, but what would be really cool is to make the substrateVM API available for regular JVM, because it is direct native access , much faster than JNI, and the API is nice to use too. Statically linking native libraries with substrateVM API is not a problem. I am already doing that in Datalevin.