SDK + IDE + GUI download pack

One tarball ships the SparkLang CPU runtime, SDK docs/APIs, VS Code-compatible editors language extension, and a graphical SPARK_BC compile / decompile app. Not CLI-only. Pack version tracks CHANGELOG (0.6.36+). CPU only.

Get the pack

Build locally: make sdk-pack (alias make dist).
Artifact: out/sdk-pack/sparklang-sdk-*.tar.gz plus out/sdk-pack/MANIFEST.json.
Site mirror (when under size cap): /downloads/sdk-pack-MANIFEST.json and the matching sparklang-sdk-*.tar.gz under Downloads.

git clone https://github.com/sparklang-dev/sparklang.git
cd sparklang
make sdk-pack
tar -tzf out/sdk-pack/sparklang-sdk-*.tar.gz | head
tar -xzf out/sdk-pack/sparklang-sdk-*.tar.gz
cd sparklang-sdk-*

What is inside

Path	Contents
`bin/spark-bootstrap`	CPU runtime — `--compile` / `--run-bc`
`bin/spark-bc-gui`	Spark IDE GUI — browse, compile/decompile/dump, split sync, Ask, weights play, report, helpers (tkinter; real `--compile` + `bc_dump`). Demo layout: ide-shell.html
`bin/spark-ide`	Opens the Spark workspace and installs the language extension in a VS Code-compatible editor (v0.2: TextMate + hover / completion / LSP diagnostics — see LSP)
`bin/spark-helper-*`	Compile, decompile, opcode sheet, fixture lint helpers
`bin/spark-shadow-*`	Shadow copy / build / verify for isolated rebuilds
`helpers/`	Helper scripts (also under `tools/spark_helpers`)
`shadows/`	Shadow utilities (also `tools/spark_shadows`)
`tools/`	BC dump, helpers, shadows, eval notes
`runtime/`	Python package, dump tools, published `.sparkbc` examples
`sdk/`	Docs, `spark_rt.h`, examples, APIs
`ide/`	VS Code-compatible editors extension + workspace
`gui/`	GUI sources

Helpers and shadows

./bin/spark-helper-compile sdk/examples/spark_builder.spark /tmp/x.sparkbc
./bin/spark-helper-decompile /tmp/x.sparkbc | head
./bin/spark-helper-opcodes
./bin/spark-helper-fixture-lint examples/fixtures/train/dataset.jsonl

./bin/spark-shadow-copy mybuild
./bin/spark-shadow-build mybuild
./bin/spark-shadow-verify mybuild # may exit 2 on golden mismatch

Helpers wrap the same real --compile / bc_dump paths as the GUI. Shadows mirror sources under out/shadow/<name>/ for isolated rebuilds. If sibling K merges a richer tools tree, make sdk-pack copies tools/spark_kit (or tools/helpers / tools/shadows) when present.

Launch the graphical compiler / decompiler

Needs a display and Python 3 with tkinter (python3-tk on Debian/Ubuntu).

# From the unpacked pack:
./bin/spark-bc-gui

# From a source checkout:
make spark-bc-gui
# or:
PYTHONPATH=tools:python ./tools/spark_bc_gui/launch.sh

In the window: edit .spark source → Compile → .sparkbc, or open a .sparkbc → readable dump (disassemble / inspect). The GUI calls the same bootstrap --compile and sparklang.model_lab.bc_dump paths as the CLI — not a mock.

Launch the IDE

./bin/spark-ide
# or from source:
make ide

See also IDE status for language ops already wired in-tree.

Verify

make test-sdk-pack # headless: pack paths + compile/decompile smoke

Related: SPARK_BC builder · All downloads.