nandi/frq · justfile

nandi/frqpublic⑂ Fork 0

⑂ f735240c84659e2c5427f3c52b5665207e08ce2a

justfile · 244 lines · 11.1 KBMakefile    Blame HistoryRaw
Inline the babashka scripts into the justfile   1# The work is here now, in recipe bodies, where it used to be in scripts/ —
2# babashka scripts run through a scripts/bb that went looking for a babashka.
3# That indirection bought one thing worth having, a shared way to reach nix on
4# a host that keeps it in a container, and `nix` below is the whole of it.
6# Every recipe that runs frq has the same shape: outside the dev shell, re-enter
7# it and come back to this same recipe; inside, hand jolt the deps overrides and
8# the library path the shell exported. The re-entry test is JOLT_NATIVE_LIB,
9# which only the shell sets — no flag to forget, and no second code path for
10# someone who runs `nix develop --command just run` by hand.
Take glimmer-vidya from gitlab, so a stranger can build this   11
Write the build in babashka, and pin the babashka   12set shell := ["bash", "-euo", "pipefail", "-c"]
A freeq client in jolt, as glimmer components on Vidya   13
Give the terminal's classpath an nREPL, and hand recipes their arguments   14# Every recipe below is a `#!` script and passes its arguments on with "$@".
15# Without this that is empty in one — just interpolates into a shebang recipe
16# rather than handing it argv — and `just tui --headless` silently ran the
17# terminal instead.
18set positional-arguments
Inline the babashka scripts into the justfile   20# nix is not on every host this runs on: on the machine these recipes were
21# written for it lives in an Arch distrobox, at the same path — which is why
22# the container is entered rather than the tree copied into it. See CLAUDE.md.
23nix := `command -v nix >/dev/null 2>&1 && echo nix || echo "distrobox enter arch -- nix"`
25# --max-jobs 0 is what sends the work to the `builders` entry rather than
26# compiling it here. Left to the default, nix prefers the local machine, and a
27# cold jolt-native is egui, openh264 and quinn on a laptop — for a derivation a
28# remote builder has likely built already. FRQ_MAX_JOBS=auto is the way out on
29# a machine with no builder configured.
30jobs := env("FRQ_MAX_JOBS", "0")
A freeq client in jolt, as glimmer components on Vidya   32
33    @just --list
Build the APK, out of ClojureDart and Flutter   35# The APK: ClojureDart compiled to Dart, then Flutter's Gradle build.
37# Impure on purpose, and worth saying why rather than leaving it to be
38# discovered. Gradle resolves its own dependencies over the network and
39# installs build-tools and a platform into ANDROID_HOME as it goes, so it
40# cannot run in a sandbox and cannot write to the store. What nix gives here
41# is the toolchain — clojure, a JDK, Flutter, and an SDK composed by
42# androidenv — and the recipe copies that SDK somewhere writable
43# (flutter/.home) for Gradle to finish off. That copy and everything Gradle
44# leaves behind are gitignored.
46# No ndkVersion in android/app/build.gradle.kts, for the same reason: the
47# Flutter template sets it, setting it makes Gradle fetch that exact NDK, and
48# there is no native code here to need one.
50#   just apk                build the debug APK
51#   just apk install        build it and put it on a connected device
52#   just apk run            install and launch
53#   just apk log            logcat, filtered to this app
54apk action="build":
55    #!/usr/bin/env bash
56    set -euo pipefail
57    cd "{{justfile_directory()}}/flutter"
59    sdk="$(nix build --impure --no-link --print-out-paths \
60        --expr 'let pkgs = import (builtins.getFlake "github:NixOS/nixpkgs/nixos-unstable") { system = "x86_64-linux"; config = { allowUnfree = true; android_sdk.accept_license = true; }; }; in (pkgs.androidenv.composeAndroidPackages { cmdLineToolsVersion = "13.0"; buildToolsVersions = [ "34.0.0" ]; platformVersions = [ "35" "34" ]; includeNDK = false; }).androidsdk')/libexec/android-sdk"
62    export HOME="$PWD/.home"
63    export ANDROID_HOME="$HOME/android-sdk"
64    export ANDROID_SDK_ROOT="$ANDROID_HOME"
65    mkdir -p "$HOME"
67    # Gradle writes into ANDROID_HOME, so it is a copy rather than the store
68    # path. Made once and kept: re-copying would throw away the build-tools
69    # and platform Gradle installed into it on the last run.
70    if [ ! -d "$ANDROID_HOME" ]; then
71        cp -r "$sdk" "$ANDROID_HOME"
72        chmod -R u+w "$ANDROID_HOME"
75    flutter="nix shell nixpkgs#clojure nixpkgs#jdk17 nixpkgs#flutter --command"
77    $flutter clojure -M:cljd compile
79    # Rewritten every run: it carries absolute store paths, and the flutter
80    # one moves whenever nixpkgs does.
81    $flutter flutter config --android-sdk "$ANDROID_HOME" >/dev/null
83    apk=build/app/outputs/flutter-apk/app-debug.apk
84    adb="${ADB:-$ANDROID_HOME/platform-tools/adb}"
86    case "{{action}}" in
87        build)   $flutter flutter build apk --debug ;;
88        install) $flutter flutter build apk --debug && "$adb" install -r "$apk" ;;
89        run)     $flutter flutter build apk --debug && "$adb" install -r "$apk" \
90                     && "$adb" shell monkey -p uk.nandi.frq -c android.intent.category.LAUNCHER 1 ;;
91        log)     "$adb" logcat -s flutter ;;
92        *)       echo "usage: just apk [build|install|run|log]" >&2; exit 1 ;;
Inline the babashka scripts into the justfile   95# Two halves, and the split is the point. The frq source is the files on disk,
Split the tree three ways, and let the phone be Flutter's   96# uncommitted edits and all. Everything under it — jolt, glimmer, glimmer-cosmic
97# and the native objects — is the flake's, built rather than fetched.
Inline the babashka scripts into the justfile   98
99# Deliberately not `nix run .#frq`. That builds the flake's own copy of the
100# source, which is the tree as git has it — so an edit that has not been
101# committed, or committed on a branch the command was not pointed at, runs as
102# whatever was there before, silently. A run meant to answer "does my change
103# work" has to be the files on disk.
Split the tree three ways, and let the phone be Flutter's   105# libcosmic paints through wgpu, so this needs nixGL off NixOS for the same
106# reason the window always did: the real driver is the host's.
108# There is no jvui and no vidya here any more — both were experiments. The
109# window is libcosmic and the terminal is libjolttui, and those are the two.
Run this tree on a native half the builders made   111# The app: this tree's source on the flake's everything-else, in the dev shell.
A freeq client in jolt, as glimmer components on Vidya   112
Inline the babashka scripts into the justfile   113    #!/usr/bin/env bash
114    set -euo pipefail
115    cd "{{justfile_directory()}}"
116    if [ -z "${JOLT_NATIVE_LIB:-}" ]; then
117        exec {{nix}} develop . --max-jobs {{jobs}} --command just run "$@"
120    deps="{:deps {jolt-lang/glimmer {:local/root \"$GLIMMER_SRC\"}"
Split the tree three ways, and let the phone be Flutter's   121    deps="$deps nandi/glimmer-cosmic {:local/root \"$GLIMMER_COSMIC_SRC\"}}}"
Inline the babashka scripts into the justfile   122
123    export LD_LIBRARY_PATH="$JOLT_NATIVE_LIB:$FRQ_LIB_PATH${LD_LIBRARY_PATH:+:$LD_LIBRARY_PATH}"
Paint the same screens into a terminal   124
Inline the babashka scripts into the justfile   125    runner=()
126    [ -e /run/current-system ] || runner=("$NIXGL")
Split the tree three ways, and let the phone be Flutter's   128    exec "${runner[@]}" jolt -Sdeps "$deps" -m frq.cosmic "$@"
Inline the babashka scripts into the justfile   129
Split the tree three ways, and let the phone be Flutter's   130# `run` with the other backend under it. Only libjolttui: `frq.app` names no
131# backend at all any more, and `frq.tui` requires glimmer-tui so the one
132# installed is the terminal.
Inline the babashka scripts into the justfile   133
134# No nixGL here, unlike `run`: a terminal wants nothing from the host's GL
135# driver, which is the reason this output exists on machines that have none.
Paint the same screens into a terminal   137# The same screens in a terminal. `just tui --headless` prints one screenshot.
138
Inline the babashka scripts into the justfile   139    #!/usr/bin/env bash
140    set -euo pipefail
141    cd "{{justfile_directory()}}"
142    if [ -z "${JOLT_NATIVE_LIB:-}" ]; then
143        exec {{nix}} develop . --max-jobs {{jobs}} --command just tui "$@"
146    deps="{:deps {jolt-lang/glimmer {:local/root \"$GLIMMER_SRC\"}"
147    deps="$deps nandi/glimmer-tui {:local/root \"$GLIMMER_TUI_SRC\"}}}"
149    export LD_LIBRARY_PATH="$JOLT_NATIVE_LIB${LD_LIBRARY_PATH:+:$LD_LIBRARY_PATH}"
Build the desktop libraries rather than fetching a release of them   150
Inline the babashka scripts into the justfile   151    exec jolt -Sdeps "$deps" -m frq.tui "$@"
Give the terminal's classpath an nREPL, and hand recipes their arguments   153# The same classpath as `tui`, with an nREPL on it instead of a `-main`: a
154# session that can require `frq.tui` and then redefine a component while it is
155# on screen, which is a second and not the minute a rebuild costs.
157#     just nrepl                      then, from an editor or a client on 7888:
158#     (require (quote frq.tui))       both backends, terminal installed last
159#     (frq.tui/-main "--headless" "--demo")
160#     (glimmer.core/reload!)          re-mount after redefining a component
162# `just repl nrepl-server` is the window's half of this — the same thing minus
163# glimmer-tui. Port is nrepl-server's own positional: `just nrepl 7889`.
164nrepl *args:
165    #!/usr/bin/env bash
166    set -euo pipefail
167    cd "{{justfile_directory()}}"
168    if [ -z "${JOLT_NATIVE_LIB:-}" ]; then
169        exec {{nix}} develop . --max-jobs {{jobs}} --command just nrepl "$@"
172    deps="{:deps {jolt-lang/glimmer {:local/root \"$GLIMMER_SRC\"}"
173    deps="$deps nandi/glimmer-tui {:local/root \"$GLIMMER_TUI_SRC\"}}}"
175    export LD_LIBRARY_PATH="$JOLT_NATIVE_LIB:$FRQ_LIB_PATH${LD_LIBRARY_PATH:+:$LD_LIBRARY_PATH}"
177    exec jolt -Sdeps "$deps" nrepl-server "$@"
Inline the babashka scripts into the justfile   179# `jolt` in the repo root does not work on its own: deps.edn carries
180# :jolt/native, so every invocation here loads libvidya and libjoltmoq before it
181# reads a line, and dies naming the library if the loader cannot find them. So
182# this is `run` without the app — and `run` is this with a window's worth of
183# extra care about the GL driver.
Build the desktop libraries rather than fetching a release of them   185# A jolt with the native libraries under it: a REPL, or `just repl nrepl-server`.
186repl *args:
Inline the babashka scripts into the justfile   187    #!/usr/bin/env bash
188    set -euo pipefail
189    cd "{{justfile_directory()}}"
190    if [ -z "${JOLT_NATIVE_LIB:-}" ]; then
191        exec {{nix}} develop . --max-jobs {{jobs}} --command just repl "$@"
194    deps="{:deps {jolt-lang/glimmer {:local/root \"$GLIMMER_SRC\"}"
Split the tree three ways, and let the phone be Flutter's   195    deps="$deps nandi/glimmer-cosmic {:local/root \"$GLIMMER_COSMIC_SRC\"}}}"
Inline the babashka scripts into the justfile   196
197    export LD_LIBRARY_PATH="$JOLT_NATIVE_LIB:$FRQ_LIB_PATH${LD_LIBRARY_PATH:+:$LD_LIBRARY_PATH}"
199    exec jolt -Sdeps "$deps" "$@"
Bind libmoq_ffi from the object's own metadata, not from its header   200
201# Regenerate src/frq/moq/raw.clj from the libmoq_ffi we actually load.
203# UniFFI embeds its interface metadata in the object, so `uniffi-bindgen
204# --library` reads the truth out of the .so rather than a header shipped
Fetch libmoq_ffi again, and keep the codecs out of Rust   205# beside it. Those differ at one version number: the published Linux and
206# Android objects are built without moq-ffi's `audio` and `video` features
207# (206 functions, no codecs), while the shipped C header describes the Apple
208# build (230). The object is the only source this recipe will accept.
Bind libmoq_ffi from the object's own metadata, not from its header   209
210# The bindgen must match the uniffi that built the object — 0.32 for moq-ffi
211# 0.3.17 — and it is built once into the scratch dir rather than pinned into
212# the flake: nothing in a normal build needs it, and a regeneration is a thing
213# done when the moq-ffi pin moves, by hand, on purpose.
215#   just gen-moq                     # the loaded library
216#   just gen-moq path/to/libmoq_ffi.so
218# Regenerate the libmoq_ffi bindings from the object's own embedded metadata.
219gen-moq lib="":
220    #!/usr/bin/env bash
221    set -euo pipefail
222    lib="${1:-${JOLT_NATIVE_LIB:-}/libmoq_ffi.so}"
223    [ -f "$lib" ] || { echo "no libmoq_ffi.so at $lib — pass one: just gen-moq <path>" >&2; exit 1; }
224    work="${TMPDIR:-/tmp}/frq-gen-moq"
225    mkdir -p "$work/ubg/src"
226    cat > "$work/ubg/Cargo.toml" <<'TOML'
227    [package]
228    name = "ubg"
229    version = "0.1.0"
230    edition = "2021"
231    [[bin]]
232    name = "uniffi-bindgen"
233    path = "src/main.rs"
234    [dependencies]
235    uniffi = { version = "0.32", features = ["cli"] }
236
237    echo 'fn main() { uniffi::uniffi_bindgen_main() }' > "$work/ubg/src/main.rs"
238    ( cd "$work/ubg" && cargo build --release -q )
239    ( cd "$work/ubg" && ./target/release/uniffi-bindgen generate \
240        --library "$lib" --language python --out-dir "$work/py" --no-format )
241    python3 tools/py2jolt.py "$work"/py/*.py > "$work/body.clj"
242    { sed -n '1,/^  (:require \[jolt.ffi :as ffi\]))$/p' src/frq/moq/raw.clj; echo; cat "$work/body.clj"; } > "$work/raw.clj"
243    mv "$work/raw.clj" src/frq/moq/raw.clj
244    echo "wrote src/frq/moq/raw.clj ($(grep -c '^(ffi/defcfn' src/frq/moq/raw.clj) entry points)"

Inline the babashka scripts into the justfile 76dcc6c nandi 11d ago	1	# The work is here now, in recipe bodies, where it used to be in scripts/ —
	2	# babashka scripts run through a scripts/bb that went looking for a babashka.
	3	# That indirection bought one thing worth having, a shared way to reach nix on
	4	# a host that keeps it in a container, and `nix` below is the whole of it.
	5	#
	6	# Every recipe that runs frq has the same shape: outside the dev shell, re-enter
	7	# it and come back to this same recipe; inside, hand jolt the deps overrides and
	8	# the library path the shell exported. The re-entry test is JOLT_NATIVE_LIB,
	9	# which only the shell sets — no flag to forget, and no second code path for
	10	# someone who runs `nix develop --command just run` by hand.
Take glimmer-vidya from gitlab, so a stranger can build this 5c40e75 nandi 19d ago	11
Write the build in babashka, and pin the babashka 34832a8 nandi 18d ago	12	set shell := ["bash", "-euo", "pipefail", "-c"]
A freeq client in jolt, as glimmer components on Vidya 4719d6f nandi 20d ago	13
Give the terminal's classpath an nREPL, and hand recipes their arguments 664397d nandi 10d ago	14	# Every recipe below is a `#!` script and passes its arguments on with "$@".
	15	# Without this that is empty in one — just interpolates into a shebang recipe
	16	# rather than handing it argv — and `just tui --headless` silently ran the
	17	# terminal instead.
	18	set positional-arguments
	19
Inline the babashka scripts into the justfile 76dcc6c nandi 11d ago	20	# nix is not on every host this runs on: on the machine these recipes were
	21	# written for it lives in an Arch distrobox, at the same path — which is why
	22	# the container is entered rather than the tree copied into it. See CLAUDE.md.
	23	nix := `command -v nix >/dev/null 2>&1 && echo nix \|\| echo "distrobox enter arch -- nix"`
	24
	25	# --max-jobs 0 is what sends the work to the `builders` entry rather than
	26	# compiling it here. Left to the default, nix prefers the local machine, and a
	27	# cold jolt-native is egui, openh264 and quinn on a laptop — for a derivation a
	28	# remote builder has likely built already. FRQ_MAX_JOBS=auto is the way out on
	29	# a machine with no builder configured.
	30	jobs := env("FRQ_MAX_JOBS", "0")
	31
A freeq client in jolt, as glimmer components on Vidya 4719d6f nandi 20d ago	32	default:
	33	@just --list
	34
Build the APK, out of ClojureDart and Flutter e2b0e6b nandi 7d ago	35	# The APK: ClojureDart compiled to Dart, then Flutter's Gradle build.
	36	#
	37	# Impure on purpose, and worth saying why rather than leaving it to be
	38	# discovered. Gradle resolves its own dependencies over the network and
	39	# installs build-tools and a platform into ANDROID_HOME as it goes, so it
	40	# cannot run in a sandbox and cannot write to the store. What nix gives here
	41	# is the toolchain — clojure, a JDK, Flutter, and an SDK composed by
	42	# androidenv — and the recipe copies that SDK somewhere writable
	43	# (flutter/.home) for Gradle to finish off. That copy and everything Gradle
	44	# leaves behind are gitignored.
	45	#
	46	# No ndkVersion in android/app/build.gradle.kts, for the same reason: the
	47	# Flutter template sets it, setting it makes Gradle fetch that exact NDK, and
	48	# there is no native code here to need one.
	49	#
	50	# just apk build the debug APK
	51	# just apk install build it and put it on a connected device
	52	# just apk run install and launch
	53	# just apk log logcat, filtered to this app
	54	apk action="build":
	55	#!/usr/bin/env bash
	56	set -euo pipefail
	57	cd "{{justfile_directory()}}/flutter"
	58
	59	sdk="$(nix build --impure --no-link --print-out-paths \
	60	--expr 'let pkgs = import (builtins.getFlake "github:NixOS/nixpkgs/nixos-unstable") { system = "x86_64-linux"; config = { allowUnfree = true; android_sdk.accept_license = true; }; }; in (pkgs.androidenv.composeAndroidPackages { cmdLineToolsVersion = "13.0"; buildToolsVersions = [ "34.0.0" ]; platformVersions = [ "35" "34" ]; includeNDK = false; }).androidsdk')/libexec/android-sdk"
	61
	62	export HOME="$PWD/.home"
	63	export ANDROID_HOME="$HOME/android-sdk"
	64	export ANDROID_SDK_ROOT="$ANDROID_HOME"
	65	mkdir -p "$HOME"
	66
	67	# Gradle writes into ANDROID_HOME, so it is a copy rather than the store
	68	# path. Made once and kept: re-copying would throw away the build-tools
	69	# and platform Gradle installed into it on the last run.
	70	if [ ! -d "$ANDROID_HOME" ]; then
	71	cp -r "$sdk" "$ANDROID_HOME"
	72	chmod -R u+w "$ANDROID_HOME"
	73	fi
	74
	75	flutter="nix shell nixpkgs#clojure nixpkgs#jdk17 nixpkgs#flutter --command"
	76
	77	$flutter clojure -M:cljd compile
	78
	79	# Rewritten every run: it carries absolute store paths, and the flutter
	80	# one moves whenever nixpkgs does.
	81	$flutter flutter config --android-sdk "$ANDROID_HOME" >/dev/null
	82
	83	apk=build/app/outputs/flutter-apk/app-debug.apk
	84	adb="${ADB:-$ANDROID_HOME/platform-tools/adb}"
	85
	86	case "{{action}}" in
	87	build) $flutter flutter build apk --debug ;;
	88	install) $flutter flutter build apk --debug && "$adb" install -r "$apk" ;;
	89	run) $flutter flutter build apk --debug && "$adb" install -r "$apk" \
	90	&& "$adb" shell monkey -p uk.nandi.frq -c android.intent.category.LAUNCHER 1 ;;
	91	log) "$adb" logcat -s flutter ;;
	92	*) echo "usage: just apk [build\|install\|run\|log]" >&2; exit 1 ;;
	93	esac
	94
Inline the babashka scripts into the justfile 76dcc6c nandi 11d ago	95	# Two halves, and the split is the point. The frq source is the files on disk,
Split the tree three ways, and let the phone be Flutter's 7070931 nandi 7d ago	96	# uncommitted edits and all. Everything under it — jolt, glimmer, glimmer-cosmic
	97	# and the native objects — is the flake's, built rather than fetched.
Inline the babashka scripts into the justfile 76dcc6c nandi 11d ago	98	#
	99	# Deliberately not `nix run .#frq`. That builds the flake's own copy of the
	100	# source, which is the tree as git has it — so an edit that has not been
	101	# committed, or committed on a branch the command was not pointed at, runs as
	102	# whatever was there before, silently. A run meant to answer "does my change
	103	# work" has to be the files on disk.
	104	#
Split the tree three ways, and let the phone be Flutter's 7070931 nandi 7d ago	105	# libcosmic paints through wgpu, so this needs nixGL off NixOS for the same
	106	# reason the window always did: the real driver is the host's.
	107	#
	108	# There is no jvui and no vidya here any more — both were experiments. The
	109	# window is libcosmic and the terminal is libjolttui, and those are the two.
	110	#
Run this tree on a native half the builders made a32699e nandi 17d ago	111	# The app: this tree's source on the flake's everything-else, in the dev shell.
A freeq client in jolt, as glimmer components on Vidya 4719d6f nandi 20d ago	112	run *args:
Inline the babashka scripts into the justfile 76dcc6c nandi 11d ago	113	#!/usr/bin/env bash
	114	set -euo pipefail
	115	cd "{{justfile_directory()}}"
	116	if [ -z "${JOLT_NATIVE_LIB:-}" ]; then
	117	exec {{nix}} develop . --max-jobs {{jobs}} --command just run "$@"
	118	fi
	119
	120	deps="{:deps {jolt-lang/glimmer {:local/root \"$GLIMMER_SRC\"}"
Split the tree three ways, and let the phone be Flutter's 7070931 nandi 7d ago	121	deps="$deps nandi/glimmer-cosmic {:local/root \"$GLIMMER_COSMIC_SRC\"}}}"
Inline the babashka scripts into the justfile 76dcc6c nandi 11d ago	122
	123	export LD_LIBRARY_PATH="$JOLT_NATIVE_LIB:$FRQ_LIB_PATH${LD_LIBRARY_PATH:+:$LD_LIBRARY_PATH}"
Paint the same screens into a terminal ab83b42 nandi 17d ago	124
Inline the babashka scripts into the justfile 76dcc6c nandi 11d ago	125	runner=()
	126	[ -e /run/current-system ] \|\| runner=("$NIXGL")
	127
Split the tree three ways, and let the phone be Flutter's 7070931 nandi 7d ago	128	exec "${runner[@]}" jolt -Sdeps "$deps" -m frq.cosmic "$@"
Inline the babashka scripts into the justfile 76dcc6c nandi 11d ago	129
Split the tree three ways, and let the phone be Flutter's 7070931 nandi 7d ago	130	# `run` with the other backend under it. Only libjolttui: `frq.app` names no
	131	# backend at all any more, and `frq.tui` requires glimmer-tui so the one
	132	# installed is the terminal.
Inline the babashka scripts into the justfile 76dcc6c nandi 11d ago	133	#
	134	# No nixGL here, unlike `run`: a terminal wants nothing from the host's GL
	135	# driver, which is the reason this output exists on machines that have none.
	136	#
Paint the same screens into a terminal ab83b42 nandi 17d ago	137	# The same screens in a terminal. `just tui --headless` prints one screenshot.
	138	tui *args:
Inline the babashka scripts into the justfile 76dcc6c nandi 11d ago	139	#!/usr/bin/env bash
	140	set -euo pipefail
	141	cd "{{justfile_directory()}}"
	142	if [ -z "${JOLT_NATIVE_LIB:-}" ]; then
	143	exec {{nix}} develop . --max-jobs {{jobs}} --command just tui "$@"
	144	fi
	145
	146	deps="{:deps {jolt-lang/glimmer {:local/root \"$GLIMMER_SRC\"}"
	147	deps="$deps nandi/glimmer-tui {:local/root \"$GLIMMER_TUI_SRC\"}}}"
	148
	149	export LD_LIBRARY_PATH="$JOLT_NATIVE_LIB${LD_LIBRARY_PATH:+:$LD_LIBRARY_PATH}"
Build the desktop libraries rather than fetching a release of them 0b81161 nandi 15d ago	150
Inline the babashka scripts into the justfile 76dcc6c nandi 11d ago	151	exec jolt -Sdeps "$deps" -m frq.tui "$@"
	152
Give the terminal's classpath an nREPL, and hand recipes their arguments 664397d nandi 10d ago	153	# The same classpath as `tui`, with an nREPL on it instead of a `-main`: a
	154	# session that can require `frq.tui` and then redefine a component while it is
	155	# on screen, which is a second and not the minute a rebuild costs.
	156	#
	157	# just nrepl then, from an editor or a client on 7888:
	158	# (require (quote frq.tui)) both backends, terminal installed last
	159	# (frq.tui/-main "--headless" "--demo")
	160	# (glimmer.core/reload!) re-mount after redefining a component
	161	#
	162	# `just repl nrepl-server` is the window's half of this — the same thing minus
	163	# glimmer-tui. Port is nrepl-server's own positional: `just nrepl 7889`.
	164	nrepl *args:
	165	#!/usr/bin/env bash
	166	set -euo pipefail
	167	cd "{{justfile_directory()}}"
	168	if [ -z "${JOLT_NATIVE_LIB:-}" ]; then
	169	exec {{nix}} develop . --max-jobs {{jobs}} --command just nrepl "$@"
	170	fi
	171
	172	deps="{:deps {jolt-lang/glimmer {:local/root \"$GLIMMER_SRC\"}"
	173	deps="$deps nandi/glimmer-tui {:local/root \"$GLIMMER_TUI_SRC\"}}}"
	174
	175	export LD_LIBRARY_PATH="$JOLT_NATIVE_LIB:$FRQ_LIB_PATH${LD_LIBRARY_PATH:+:$LD_LIBRARY_PATH}"
	176
	177	exec jolt -Sdeps "$deps" nrepl-server "$@"
	178
Inline the babashka scripts into the justfile 76dcc6c nandi 11d ago	179	# `jolt` in the repo root does not work on its own: deps.edn carries
	180	# :jolt/native, so every invocation here loads libvidya and libjoltmoq before it
	181	# reads a line, and dies naming the library if the loader cannot find them. So
	182	# this is `run` without the app — and `run` is this with a window's worth of
	183	# extra care about the GL driver.
	184	#
Build the desktop libraries rather than fetching a release of them 0b81161 nandi 15d ago	185	# A jolt with the native libraries under it: a REPL, or `just repl nrepl-server`.
	186	repl *args:
Inline the babashka scripts into the justfile 76dcc6c nandi 11d ago	187	#!/usr/bin/env bash
	188	set -euo pipefail
	189	cd "{{justfile_directory()}}"
	190	if [ -z "${JOLT_NATIVE_LIB:-}" ]; then
	191	exec {{nix}} develop . --max-jobs {{jobs}} --command just repl "$@"
	192	fi
	193
	194	deps="{:deps {jolt-lang/glimmer {:local/root \"$GLIMMER_SRC\"}"
Split the tree three ways, and let the phone be Flutter's 7070931 nandi 7d ago	195	deps="$deps nandi/glimmer-cosmic {:local/root \"$GLIMMER_COSMIC_SRC\"}}}"
Inline the babashka scripts into the justfile 76dcc6c nandi 11d ago	196
	197	export LD_LIBRARY_PATH="$JOLT_NATIVE_LIB:$FRQ_LIB_PATH${LD_LIBRARY_PATH:+:$LD_LIBRARY_PATH}"
	198
	199	exec jolt -Sdeps "$deps" "$@"
Bind libmoq_ffi from the object's own metadata, not from its header 9f081a1 nandi 9d ago	200
	201	# Regenerate src/frq/moq/raw.clj from the libmoq_ffi we actually load.
	202	#
	203	# UniFFI embeds its interface metadata in the object, so `uniffi-bindgen
	204	# --library` reads the truth out of the .so rather than a header shipped
Fetch libmoq_ffi again, and keep the codecs out of Rust f518938 nandi 9d ago	205	# beside it. Those differ at one version number: the published Linux and
	206	# Android objects are built without moq-ffi's `audio` and `video` features
	207	# (206 functions, no codecs), while the shipped C header describes the Apple
	208	# build (230). The object is the only source this recipe will accept.
Bind libmoq_ffi from the object's own metadata, not from its header 9f081a1 nandi 9d ago	209	#
	210	# The bindgen must match the uniffi that built the object — 0.32 for moq-ffi
	211	# 0.3.17 — and it is built once into the scratch dir rather than pinned into
	212	# the flake: nothing in a normal build needs it, and a regeneration is a thing
	213	# done when the moq-ffi pin moves, by hand, on purpose.
	214	#
	215	# just gen-moq # the loaded library
	216	# just gen-moq path/to/libmoq_ffi.so
	217	#
	218	# Regenerate the libmoq_ffi bindings from the object's own embedded metadata.
	219	gen-moq lib="":
	220	#!/usr/bin/env bash
	221	set -euo pipefail
	222	lib="${1:-${JOLT_NATIVE_LIB:-}/libmoq_ffi.so}"
	223	[ -f "$lib" ] \|\| { echo "no libmoq_ffi.so at $lib — pass one: just gen-moq <path>" >&2; exit 1; }
	224	work="${TMPDIR:-/tmp}/frq-gen-moq"
	225	mkdir -p "$work/ubg/src"
	226	cat > "$work/ubg/Cargo.toml" <<'TOML'
	227	[package]
	228	name = "ubg"
	229	version = "0.1.0"
	230	edition = "2021"
	231	[[bin]]
	232	name = "uniffi-bindgen"
	233	path = "src/main.rs"
	234	[dependencies]
	235	uniffi = { version = "0.32", features = ["cli"] }
	236	TOML
	237	echo 'fn main() { uniffi::uniffi_bindgen_main() }' > "$work/ubg/src/main.rs"
	238	( cd "$work/ubg" && cargo build --release -q )
	239	( cd "$work/ubg" && ./target/release/uniffi-bindgen generate \
	240	--library "$lib" --language python --out-dir "$work/py" --no-format )
	241	python3 tools/py2jolt.py "$work"/py/*.py > "$work/body.clj"
	242	{ sed -n '1,/^ (:require \[jolt.ffi :as ffi\]))$/p' src/frq/moq/raw.clj; echo; cat "$work/body.clj"; } > "$work/raw.clj"
	243	mv "$work/raw.clj" src/frq/moq/raw.clj
	244	echo "wrote src/frq/moq/raw.clj ($(grep -c '^(ffi/defcfn' src/frq/moq/raw.clj) entry points)"