#make

Observed Wasm profile (2026-09-03): this README is supplementary. The support record is the only capability authority; it lists the repeatable moon run --target wasm --release results and exclusions. Options mentioned here but not promoted in that record are not compatibility guarantees.

cli/make provides a measured Make subset. The Wasm audit verified one target/dependency rule, an included variable, command-line variable precedence, dry run, recipe execution, and silent mode.

include, -include, sinclude, command-line variable assignment, ifeq/ifneq/ifdef/ifndef, pattern/static-pattern dependencies, and automatic variables ($@, $<, $^, $+, $*, $@D, $@F, $<D, $<F) are supported in the measured slice. -j is accepted with bounded sequential execution, -k continues independent targets after recipe failures, and -W marks targets depending on the named file out of date. The full GNU built-in database, jobserver, secondary expansion, and complete parallel scheduling remain unverified. The observed Wasm -C path selects the Makefile, but recipe process lookup and working directory remain controlled by the Wasm host; do not assume GNU make -C recipe-directory parity.

Each external command in a recipe is launched through the policy-visible MoonBit process API. Unsupported Make extensions fail explicitly; the complete Makefile is never forwarded to a host make executable. The remaining language surface is listed in the support record.

Wasm recipes start from the explicit restricted environment and remain subject to the host process policy. Native inheritance is outside this Wasm support record.