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)
@rahul080327 @borkdude a bit more on the api-ms-* dlls. they (at least some of them) exist in win10 (i think a default installation) in at least 2 places: c:\windows\system\downlevel and c:\windows\syswow64\downlevel however, comparing their versions to those that seem to make clj-kondo.exe work show that they (at least some of them) differ. i tried modifying PATH so these seemingly comes-with-the-system versions get used when executing clj-kondo.exe, but they don't seem to help. perhaps it's the specific versions that come with things like openjdk that make things work...
i wonder if there's some tweaking that can be done on the graal / native image end so that the created binary will work with what comes with windows 10...then possibly we don't have to bundle any dlls? by name, afaict, all of the dlls that appear to be necessary seem to come with windows 10 (see above).