This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2023-05-26
Channels
- # ai (1)
- # announcements (7)
- # babashka (2)
- # beginners (23)
- # biff (3)
- # calva (1)
- # chlorine-clover (3)
- # cider (2)
- # clj-kondo (12)
- # clojure (25)
- # clojure-brasil (4)
- # clojure-europe (33)
- # clojure-nl (1)
- # clojure-norway (7)
- # clojure-uk (1)
- # clojurescript (30)
- # clr (6)
- # consulting (1)
- # cursive (14)
- # data-science (1)
- # datalevin (4)
- # datomic (3)
- # events (4)
- # graphql (1)
- # gratitude (2)
- # hoplon (10)
- # inf-clojure (3)
- # interceptors (1)
- # introduce-yourself (1)
- # off-topic (13)
- # pathom (2)
- # pedestal (12)
- # rdf (14)
- # releases (6)
- # sci (17)
- # shadow-cljs (12)
If anyone is interested in how to handle dependencies using standard .NET tooling have a look here:
https://github.com/Dangercoder/clojure-clr-dotnet-api/blob/master/user.cljr
This namespace loads assemblies (the whole dependency graph) by using the output that's given to us by dotnet restore
.
This means that you can use the .NET CLI
that comes out of the box. E.g. add clojure.data.json
dotnet add package clojure.data.json --version 2.4.1
user.cljr will load this automatically (and any dependencies).👏 4
🙌 2
This is only tested on Ubuntu btw.
The lower-case usage might break things on Windows
I just started clojure.main in the root of the repo and it started up just fine. A lot of assemblies loaded.
Thanks for testing it, now I can say "It works on our machines" 😄