This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2021-03-08
Channels
- # announcements (6)
- # beginners (100)
- # calva (17)
- # cljs-dev (31)
- # cljsrn (2)
- # clojars (3)
- # clojure (137)
- # clojure-australia (1)
- # clojure-europe (41)
- # clojure-gamedev (3)
- # clojure-italy (1)
- # clojure-nl (3)
- # clojure-poland (16)
- # clojure-serbia (7)
- # clojure-taiwan (1)
- # clojure-uk (10)
- # clojurescript (10)
- # cursive (25)
- # data-oriented-programming (4)
- # datomic (26)
- # fulcro (39)
- # graalvm (6)
- # jobs (2)
- # jobs-discuss (2)
- # kaocha (19)
- # klipse (1)
- # leiningen (3)
- # lsp (18)
- # malli (21)
- # meander (26)
- # off-topic (29)
- # pathom (39)
- # polylith (3)
- # practicalli (2)
- # re-frame (11)
- # reitit (8)
- # rewrite-clj (7)
- # sci (11)
- # shadow-cljs (44)
- # sql (8)
- # tools-deps (32)
- # xtdb (3)
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?
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
That’s interesting @ericdallo ! I forget, did we go over what happens when multiple libs each have their own configs?
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 😅