nandi/jolt-nativepublic Fork 0
4f920afa410da72bfdb7a07d7faa0264c7bb8a08
Commits
Clone
git clone https://git.rickub.com/nandi/jolt-native.git
git clone ssh://git@rickub.com/nandi/jolt-native.git

Host key fingerprint (ed25519): SHA256:iycHnxEyq0Q7uyVpB7JlznP0G7JrTPXLYRcAU5CSLhc — verify it before your first connect.

Move the jolt libraries under glimmer-backends 19df0d8 · on 4f920afa410da72bfdb7a07d7faa0264c7bb8a08 · nandi · 12d ago
deps.edn · 26 lines · 1.2 KBClojure Blame HistoryRaw
 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
{:paths ["src"]

 ;; glimmer-tui is a backend for glimmer, beside glimmer-vidya and against the
 ;; same reconciler: glimmer owns the reactive core and knows about no toolkit,
 ;; and this project supplies widgets, painting and the frame loop — through
 ;; libjolttui's retained-tree C ABI (crates/jolt-tui/include/jolttui.h), which
 ;; is libvidya's tree ABI with a terminal under it instead of a GPU window.
 ;;
 ;; So an app that renders with glimmer-vidya renders here by requiring this
 ;; namespace instead. What it loses is what a terminal has not got: pictures,
 ;; a pointer, a window title, a clipboard.
 :deps {jolt-lang/glimmer {:git/url "https://github.com/jolt-lang/glimmer"
                           :git/tag "v0.1.0"
                           :git/sha "5581c331c51aff989259b9e8e92ec920fe5e6741"}}

 ;; libjolttui, built from ../../crates/jolt-tui. Put it on the search path:
 ;;   cargo build --release -p jolt-tui
 ;;   LD_LIBRARY_PATH=../../target/release jolt -M:counter
 :jolt/native [{:name "jolttui"
                :darwin ["libjolttui.dylib"]
                :linux ["libjolttui.so"]}]

 :aliases {:counter {:extra-paths ["examples"]
                     :main-opts ["-m" "glimmer-tui.counter"]}}

 :tasks {counter "jolt -M:counter"}}