M2make — build-order tutorial

M2make is a small build front-end for the V3 M2 compiler and for GNU Modula-2. Given a main source file, it follows IMPORT/FROM imports, topologically sorts the modules, and runs the compiler in the right order.

M2make [-n] [-v] [-c m2|gm2] [-I dir] [-o out]
       [--m2bin path] [--shim path] [--extra path]
       [--m2flag flag] [--dialect pim|iso|gm2] [--separate] main.mod

Build

The portable source is tools/m2make/M2make.mod; the OS bridge is m2make_os.c. From the repository root:

cd tools/m2make
./build_m2.sh       # dogfood build with the V3 M2 compiler
./build_gm2.sh      # optional: build with GNU Modula-2

Both produce a M2make binary; the dogfood binary is tools/m2make/b_v3/M2make.

One-shot build (default)

tools/m2make/b_v3/M2make \
    --m2bin ./compiler/M2 \
    --shim runtime/syslib/shim.c \
    -o /tmp/prog prog.mod

For V3 this runs one M2 session over all .def/.mod files, then qbe, then cc with the runtime shim. It gates on M2’s Parsed correctly verdict.

Separate-object build

tools/m2make/b_v3/M2make --separate \
    --m2bin ./compiler/M2 \
    --shim runtime/syslib/shim.c \
    --dialect iso \
    -o /tmp/prog prog.mod

Each module is compiled with M2 -c -I ...; M2 resolves the target’s .def and imported interfaces transitively. The program object contains main, library objects contain only their code plus <Module>_init. All objects are linked with cc and the shim. Stale objects are rebuilt from their source/interface mtimes, a newer compiler binary is treated as an ABI event, and the link is redone when an object or the shim changes.

Options

-n — dry run: print the build order and command.
-v — verbose: report external modules and build order.
-c m2|gm2 — compiler driver (default m2).
-I dir — extra search directory (repeatable; the main file’s directory is always searched).
-o out — output executable (default: program module name).
--m2bin path — M2 driver (default M2).
--shim path — C runtime shim for V3 mode (default shim.c).
--extra path — extra C file linked after the shim.
--m2flag flag — one extra M2 argument (the fixpoint uses -legacyopen1d).
--dialect pim|iso|gm2 — add lib/<dialect>, lib/common, lib/gm2 and runtime/syslib to the search path. Use one dialect per session.
--separate — per-module objects instead of one session image.

Current limits

Incremental object checks use mtimes, not a content-based ABI marker.
Type/value/procedure and generic-class instances are built as separate objects.
The default one-shot mode remains the mode used by the suite, corpus and self-hosting fixpoint.
M2 -c resolves imported interfaces through -I; explicit interface lists remain supported.

See TUTORIAL.md, docs/separate-compilation.md, and tools/m2make/README.md for details.

m2make.md 2.9 KB Historie Surový