GraalVM, and especially Native Image, is an impressive and important
project, but more limited than many imagine.
Building native images is constrained by practical issues. For example,
running a Java application requires certain external dependencies. If a
dependency is not available, then the application may fail, but
generally only at the point of invoking a specific feature that
requires it. If some feature is not invoked, then a missing dependency
may be harmless.
Dependency resolution is different for Native Image. Rather, the tool
attempts to find the complete set of dependencies utilized at all
points in an application, convert them all into native machine code,
and finally, bundle them into a single executable file.
Native Image is less useful for consumers of a Java application than
developers. It might require integration of NI into the overall build
process, to achieve the results you want.
On Thu, Dec 1 2022 at 11:08:32 AM +0100, dli...@gmail.com wrote:
Hello Everyone,
Didn't anybydy try and is that possible to convert the BaseX JAR to a
"native-image" (using GraalVM's convertor or any other tool maybe)?
The reason: I have to use BaseX in scripts and Makefiles as an XQuery
engine and have to call it often. The problem is the JVM startup time
affects the performance significantly when it has to start multiple
times.
I tried just naïvely running the GraalVM's native-image convertor
against the BaseX103.jar file and got errors with long backtraces
(that
I didn't quite understand to be honest).
Did anybody try that, maybe?
Best regards
