This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2023-02-14
Channels
- # announcements (7)
- # babashka (13)
- # beginners (98)
- # biff (20)
- # calva (3)
- # clj-kondo (5)
- # clj-otel (6)
- # cljs-dev (96)
- # clojure (22)
- # clojure-austin (29)
- # clojure-conj (4)
- # clojure-europe (53)
- # clojure-nl (2)
- # clojure-norway (63)
- # clojure-uk (3)
- # clojurescript (18)
- # cursive (10)
- # data-science (11)
- # datalevin (2)
- # datomic (7)
- # deps-new (1)
- # fulcro (3)
- # graphql (1)
- # gratitude (4)
- # hyperfiddle (43)
- # kaocha (4)
- # malli (15)
- # pathom (6)
- # polylith (2)
- # reagent (3)
- # reitit (2)
- # releases (6)
- # remote-jobs (1)
- # rewrite-clj (45)
- # ring (4)
- # shadow-cljs (47)
- # sql (5)
- # xtdb (8)
I'm attempting to use clj-kondo as a dependency in a library that i'll compile with GraalVM. It seems that the META-INF files are being picked up by graalvm and used, and it ends up just building a version of clj-kondo on my machine instead compiling my library lol. any suggestions on how to avoid this?
Maybe it's because of this? https://github.com/clj-kondo/clj-kondo/blob/master/resources/META-INF/native-image/clj-kondo/clj-kondo/native-image.properties
Are you sure it's building clj-kondo, and not just your project but with the name clj-kondo?
it spit out a clj-kondo bin and when i ran clj-kondo --help it printed the clj-kondo help text lol. looking at your git history, i think i see the changes necessary (moving some of the native-image.properties flags back to my call).