graalvm

Discuss GraalVM related topics. Use clojure 1.10.2 or newer for all new projects. Contribute to https://github.com/clj-easy/graal-docs and https://github.com/BrunoBonacci/graalvm-clojure. GraalVM slack: https://www.graalvm.org/slack-invitation/.
ericdallo 2021-03-08T13:26:11.099100Z

I https://github.com/clojure-lsp/clojure-lsp/commit/0f0382de91ede9a67b7fff72c221375e66160735 to have the configs inside the META-INF folder, this way it's added to the jar, I think I'll make that for lsp4j since I had a hard time with that in the past when compiling clojure-lsp, this way any lib using lsp4j will use the correct args/configs for graalvm OOTB ๐Ÿ™‚ @borkdude Do you think we should that for clj-kondo as well?

ericdallo 2021-03-08T13:30:50.100500Z

Maybe we should mention this https://www.graalvm.org/reference-manual/native-image/BuildConfiguration/#embedding-a-configuration-file of compiling with native-image on the clj-graal-docs @lee? Eventually more and more libs will have support for graalvm and doing this way make things work OOTB

lread 2021-03-08T13:40:33.102400Z

Thatโ€™s interesting @ericdallo ! I forget, did we go over what happens when multiple libs each have their own configs?

ericdallo 2021-03-08T13:41:46.103300Z

the graalvm docs mention you should organize it with a directory hierarchy of groupId and artifactId, but I don't know what happens if 2 libs set the same flag with different values ๐Ÿ˜…

ericdallo 2021-03-08T13:42:10.103900Z

But that's easy to repro, as soon you start to compiling, graalvm will print the flags used

borkdude 2021-03-08T14:00:08.104100Z

yes