This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2019-06-27
Channels
- # announcements (5)
- # beginners (267)
- # boot (1)
- # calva (37)
- # cider (11)
- # clara (10)
- # clj-kondo (24)
- # cljsrn (13)
- # clojars (1)
- # clojure (119)
- # clojure-europe (5)
- # clojure-italy (19)
- # clojure-nl (11)
- # clojure-spec (18)
- # clojure-uk (99)
- # clojurescript (44)
- # clojurex (57)
- # community-development (6)
- # cursive (13)
- # datomic (92)
- # duct (12)
- # fulcro (1)
- # graalvm (4)
- # jobs (1)
- # kaocha (6)
- # luminus (3)
- # lumo (9)
- # off-topic (20)
- # pathom (6)
- # re-frame (21)
- # reagent (2)
- # reitit (9)
- # remote-jobs (4)
- # shadow-cljs (32)
- # spacemacs (3)
@hlolli i am trying to get the pkg-lumo sample to work, but am encountering errors which i have so far failed to understand: https://pastebin.com/uiny0Ax5 -- any hints?
I've never seen such an error before, wow. I guess if you have a node project collects dust, it will start behaving weirdly.
it needs an update for sure, still compiling against an old lumo version, just didn't know anybody used it except the closh project.
i need to look into using an older node version -- thanks for the hint. am quite interested in pkg-lumo as a potential alternative to native-image for writing some tooling
yes, I'm all for single binary, it's almost as good as statically compiled the result, since as far as I remember, only libc is required. I got a crush on graal's native-image for that reason.
But graal has some llvm files that must be included when using polyglot, but not a big deal