This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2022-12-30
Channels
- # aleph (25)
- # announcements (20)
- # babashka (29)
- # babashka-sci-dev (12)
- # beginners (27)
- # biff (3)
- # clojure (29)
- # clojure-europe (21)
- # clojure-nl (1)
- # clojure-norway (1)
- # clojurescript (3)
- # clr (5)
- # code-reviews (4)
- # data-science (7)
- # datahike (6)
- # datascript (3)
- # emacs (9)
- # fulcro (5)
- # graalvm (10)
- # malli (15)
- # nbb (7)
- # off-topic (17)
- # pathom (9)
- # polylith (4)
- # practicalli (15)
- # reitit (3)
- # releases (2)
- # rum (1)
- # shadow-cljs (73)
- # squint (34)
- # tools-deps (3)
- # xtdb (11)
I haven’t done any graalvm builds myself, so sorry if this is a newbie question, but should JNI using libraries work out of the box with graalvm? I’m thinking specifically about RocksDB (the fat jar has linux, windows and mac libs baked in)
You can make JNI work but probably not out of the box unless there is a known configuration for it
if I need to delve into the internals of rocksdb jni, it sounds like it might be quite a lot of work
It seems quarkus has support for Kafka streams so this probably means you could copy something or something might already be available in the registry
you can also use the graal tracing agent https://www.graalvm.org/latest/reference-manual/native-image/metadata/AutomaticMetadataCollection/ along with a similar agent for clojure https://github.com/luontola/clojure-native-image-agent the graal tracing agent can generate JNI and other config from running your program