refactor(cli)!: split the contributor tool out of the ludic CLI
`ludic help` ended with a section titled "contributing to the toolchain itself", listing bootstrap, reseed, docs-gen and release tasks. None of that is available to someone who installed the language — those tasks need the repository — so the shipped tool was advertising work its user cannot do, in a namespace they have to read past to find `new` and `run`. The tasks move to a second program, dev.ludic -> bin/ludic-dev, built from a checkout and excluded from every release artifact. `ludic` keeps the project and package commands and nothing else; `ludic dev …` now explains where the tasks went instead of failing as an unknown command. What this shook out: the two programs share prelude/build/project/pkg, so the helpers each had accreted in whichever file first needed them — cc(), ensure_ludicc, the string functions, title_case, cmd_version — moved to where both can see them. The argument-shift indirection added for the `dev` namespace is gone with the namespace, so commands read argv directly again. `ludic-dev test` asserts the split rather than trusting it: the staged install must build a project, and `ludic dev build` there must fail while naming ludic-dev. install.sh keeps building older tags, whose bootstrap goes through main.ludic. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This commit is contained in:
parent
f369fbd227
commit
e175619543
46 changed files with 630 additions and 558 deletions
|
|
@ -12,7 +12,7 @@
|
|||
#
|
||||
# This is the compiler, not the command line a user of the language meets: that
|
||||
# is `ludic` (tools/ludic-cli), which drives this. With no -o and no --run, IR
|
||||
# still goes to stdout — the contract `ludic dev reseed` and `ludic dev
|
||||
# still goes to stdout — the contract `ludic-dev reseed` and `ludic dev
|
||||
# bootstrap` rely on, so the bootstrap is untouched.
|
||||
|
||||
# basename: the part of a path after the last '/'.
|
||||
|
|
@ -124,7 +124,7 @@ entry {
|
|||
|
||||
# a game gets a window by default; a plain program stays headless. An explicit
|
||||
# flag always wins. The stdout-IR path (no target) also stays headless, which
|
||||
# is what `ludic dev reseed` compiles the compiler itself with.
|
||||
# is what `ludic-dev reseed` compiles the compiler itself with.
|
||||
let has_target = run or (out != null)
|
||||
if want == 1 { g_windowed = true }
|
||||
else if want == 2 { g_windowed = false }
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue