Orkuncakilkaya
aca263642d
Getting started meant cloning the repository, bootstrapping a compiler and
learning a task runner called `x`. That is a contributor's workflow handed to
everyone who wants to try the language.
Installing is now one command:
curl -fsSL https://workshopsoft.pages.workshopsoft.io/ludic/install.sh | sh
install.sh puts a complete toolchain — compiler, CLI, engine runtime, bundled
ludic.* packages, formatter, language server — in ~/.ludic and adds it to PATH.
Prebuilt artifacts are checksum-verified; where a platform has none, or the
release predates this layout, it bootstraps from the compiler's own IR seed with
clang. The docs site publishes the script beside the pages that quote it, so the
page and the script can never come from different releases.
`x` becomes `ludic`, and the surface splits by audience. A user of the language
sees `new`, `run`, `build`, `test`, `add`, `fmt`, `lsp`, `doctor`, `upgrade`;
`ludic new` scaffolds a project that builds and plays as it stands. Everything
the toolchain repo needs moved under `ludic dev` — build, test, reseed,
bootstrap-cfree, docs-gen, release — unchanged apart from the namespace. Those
tasks read arguments one position further along, so dispatch_dev sets a shift
and commands use arg_n()/arg_total() rather than each knowing its own depth.
Release artifacts become complete install roots (bin/ beside runtime/, packages/
and VERSION) rather than bare binaries, which is what the installer unpacks.
`ludic dev test` asserts the whole shape: it stages an install, puts it on PATH
with no LUDIC_HOME, and runs new -> build -> test through it.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
49 lines
1.8 KiB
Text
49 lines
1.8 KiB
Text
# Generated build tree: LLVM IR, objects, compiled apps, the headless render
|
|
# (build/out.ppm) and the docs site all land under build/ (see `bin/ludic dev build` /
|
|
# `bin/ludic clean`). Root-anchored so a source dir named "build" elsewhere is never
|
|
# accidentally ignored. Nothing is written to the repo root any more.
|
|
/build/
|
|
|
|
# Archives are never tracked: the Kenney art is committed *extracted* under
|
|
# assets/kenney/**/ (PNG/tmx/License), while the original download .zips and any
|
|
# packaged plugin .zip are local-only build inputs/outputs.
|
|
*.zip
|
|
|
|
# the toolchain binaries (ludicc, ludic, ludic-fmt, ludic-lsp) — all built
|
|
# into bin/ by the one-line bootstrap + `bin/ludic dev build`; never checked in. The
|
|
# only thing published is the source and the LLVM-IR seed (selfhost/ludicc.seed.ll).
|
|
/bin/
|
|
|
|
# package manager (issue #63): the per-project linked view into the global
|
|
# content-addressed store, and the optional hermetic copy from `ludic vendor`. Both
|
|
# are regenerated by `ludic get` / `ludic vendor` — package.ludic + package.lock.ludic
|
|
# are the tracked source of truth, so these stay out of the tree.
|
|
ludic_modules/
|
|
vendor/
|
|
|
|
# editor toolchain build artifacts
|
|
tools/editors/vscode/node_modules/
|
|
tools/editors/vscode/*.vsix
|
|
tools/editors/jetbrains/.gradle/
|
|
tools/editors/jetbrains/build/
|
|
|
|
# IntelliJ plugin SDK sandbox (tools/editors/jetbrains)
|
|
.intellijPlatform/
|
|
.idea/
|
|
|
|
# macOS Finder metadata
|
|
.DS_Store
|
|
**/.DS_Store
|
|
|
|
# Python bytecode cache from the docgen / release tooling
|
|
__pycache__/
|
|
*.pyc
|
|
|
|
# Release artifacts produced by `ludic dev release`
|
|
/dist/
|
|
|
|
# Build/release tarballs anywhere in the tree. `git -C <repo> archive -o foo.tgz`
|
|
# resolves -o relative to the repo, not the caller's directory, so a stray
|
|
# archive lands in the root and a blanket `git add -A` will commit it.
|
|
*.tar.gz
|
|
*.tgz
|