Repository navigation
Releases
Bootstrap pyre v1.14.0
This release bootstraps pyre v1.14.0.
Changes
- The bootstrap fetches the pyre v1.14.0 boot bundle (
87ee95b). When mm cannot importpyre, it downloadspyre-boot.zipfrom the pyre v1.14.0 release instead of v1.13.1.
Clean activation output on a first run
This release fixes the output of mm --activate on the first run of a checkout in an environment where pyre is not importable.
Fixes
- The bootstrap announces its download on stderr (
1ea8d21). When mm cannot importpyre, it downloads the boot bundle and used to say so on stdout, ahead of theexportstatements--activateprints, in a message whose quote was never closed.eval "$(mm --activate ...)"then failed withunexpected EOF while looking for matching '. The message now goes to stderr and closes its quote, so the output of--activateis shell code on every run.
Suite cases, checks in every mode, and production web bundles
This release lets a test suite run its drivers against several configurations, keeps the checks
of compiled test drivers live in every build mode, builds web bundles for production in the
deployment modes, and adds a fedora install mode with an rpm package database, code coverage,
and the target factory for pure python boot bundles.
Breaking changes
- GNU make 4.4 or later is required: the engine orders prerequisites with
.WAIT
(1d69d67). Older versions stop with a message that names the floor. - The build mode decides whether the developer checks are compiled in, not the optimization
target (#52):devdefinesDEBUG,releaseand the deployment modes defineNDEBUG, and
exactly one of the two is defined in every build. The default localoptbuild used to define
neither, anddebugused to defineDEBUG.--assertionspins the choice on the command line
(#53). - Test drivers compile with their checks on in every mode (#66). A compiled driver that
depended onNDEBUGin a deployment mode builds withDEBUGnow; a suite opts out with
<suite>.assertions := no, a driver withtests.<...>.assertions := no. mm does not rebuild a
product when only its flags change, so clean the test suites, or the build area, once after
upgrading. - The rpath lists its directories in the order of their sources, the order the libpath uses,
instead of alphabetically (#65). A product that used to find a library in a shared location
ahead of the build's own area now finds the one it was built against.
Tests
- A suite can declare
casesthat every one of its drivers runs, each with its ownharness
andargv, unless a driver names cases of its own;mm <suite>.infolists them (#64). - Test suites can name additional areas their clean target removes (
992c108). - The staged copy of a driver resolves the externals of its suite after the package database
is loaded (791fd07).
Build modes
- A
fedorainstall mode with canonical locations (67167b6,93fab6e). - The deployment modes build web bundles for production: webpack sees
NODE_ENV=production,
andmode.inforeports it (#58).
Package databases and externals
- An
rpmpackage database for the fedora and rhel family (0e119a2). dpkgfinds the parallel flavors of hdf5 and mpi in their subdirectories (#49,de9c1c8) and
the libpq headers underpostgresql(#50).- conda: the python ABI suffix comes from the package manifest (#47); cuda is found by locating
nvcc,cuda_runtime.h, andlibcudart, and its paths come from their common root
(1fe5ee5,d4de241);hdf5.parallelis derived for conda and macports (0bfe0f2). - The externals of a child library resolve once the package database is loaded (
4dbb7a2).
Web clients
- A build that changes nothing does nothing: the configuration and the lock of a bundle are
its prerequisites, and the recipes mark the bundle and the modules as current (#59, #60). - The clean target of a web client removes the installed client, not only its staging area
(9808e1e); the clean target of a package removes its installed drivers and configuration
files (fb36742).
Toolchains
- Playwright 1.63.0, with chromium, webkit, and firefox (#54), and
mm-playwright, which tells a
suite what the browsers of the toolchain need on each platform (fb93dc6,61b591b).
Code coverage
covis a build variant:mm --target=cov,shared <suite>builds and runs the tests with the
compiled languages instrumented, in a build root and prefix of their own, and
mm --target=cov,shared coveragemerges the data and renders a terminal summary, an HTML tree,
and an lcov file (#51).
Bundles and bootstrap
- The
boottarget factory builds pure python bootstrap archives, with an optionalboot.main
staged as the archive's__main__.py(2ed9f5e, #46);zipand its bundle flags are
available to recipes (f1666a5). - The bootstrap downloads the pyre v1.13.1 boot bundle when pyre is not importable (#55, #63).
- A child
mmrelaunches through the driver, and forwards--portinfo; the darwin platforms
honorSDKROOTbefore falling back to the command line tools SDK (#56). mm.homecomes from the make engine, so paths do not depend on how mm was deployed (bdaca1c).
Other
- The shell completions know the
bootand library.gentargets (e08daf7,a20becf,
cdade9c); clean targets log one line per area (17476f2). - The preambles of every file conform to the standard, and the comments are spell checked (#48).
Full Changelog: v5.3.0...v5.4.0
Build modes, dependency-aware externs, and shared toolchains
Build modes
mode is now a first-class build axis that drives recipe behavior, not just product paths. Adds a local release mode (alongside dev/conda/macports/ubuntu) and exposes project.mode to the make engine.
make/modes/— one file per mode inheriting a shareddefault; recipes read named, consumer-grouped knobs (e.g.mode.npm.locked) instead of branching on the mode name. Selecting an unimplemented mode fails loudly;mode.info/mode.helpreport the active configuration.- npm lockfile policy (webpack + vite) —
devresolves dependencies fresh (npm i); deployment modes install exactly from a committedpackage-lock.json(npm ci). New<pack>.lock.seed(force a clean install from the committed lock, to recover from npm instability) and<pack>.lock.harvest(promote a freshly-resolved lock back to source) targets. The install is keyed onnode_modules/, so a missing install always re-runs.
External packages
- Dependency-aware loading —
extern.closureresolves a project's externals via a topo-sorted walk of<pkg>.dependencies(e.g. parallel HDF5 pulls in MPI). - Marker verification —
extern.verify/extern.<pkg>.verifyprobe the resolved include/lib paths via per-package header and required markers, catching breakage a package-database check cannot see and honoring adhoc overrides. - Hygiene — conda-recipe coverage check with an exception registry; canonical
yaml(C libyaml) split fromyaml-cpp; whole-word membership tests eliminate name collisions (metis/parmetis, yaml/yaml-cpp). New guide for adding an external package.
Toolchains
- Environment-
8000
level developer toolchains — installed once per environment and declared (not owned) by projects; new
toolchainstrait emitted to the make engine. - Vendor toolchains — a new
vendorkind with a docker toolchain (docker-images routed through it); test suites can declare and consume a toolchain; live vendor-version reporting; quieter Playwright on recent Node.
Other
- New
openmpbuild variant. - Fortran/flang mixed-build fixes (drop unsupported
-pipe, linkflang_rt.runtime). - webpack: opt-in schema generation with on-demand generate/clean targets.
- Stop publishing the extension support archive; shell-statement quoting fixes for
--activate/--branch; libtorch external with optional CUDA libraries; assortedexamples/hellorepairs.
What's Changed
- Add an openmp build variant (#16) by @aivazis in #36
- Add TorchScript support to mm by @trulko in #23
- toolchains: environment-level developer tool support (first: playwright) by @aivazis in #37
- extern: improves the handling of external dependencies in a conda environment by @aivazis in #38
- Use playwright as an example toolchain member and test runner by @aivazis in #39
- make/extern: follow package .dependencies to compute a project's external dependencies by @aivazis in #40
- docs: add a guide for adding support for an external package by @aivazis in #41
- Added support for flang by @aivazis in #42
- Add support for optional CUDA libraries in libtorch by @trulko in #43
- The make layer is now aware of the build mode by @aivazis in #45
Full Changelog: v5.2.0...v5.3.0
Improved support for package discovery and modern test runners
Highlights
- Self-discovering test runners — a new runner abstraction that drives framework-native test discovery (Playwright, Vitest, pytest, Catch2, gtest) instead of per-file drivers.
- On-disk conda/mamba package discovery — the conda pkgdb now reads conda-meta directly instead of shelling out to an agent that's usually not on PATH.
- CUDA as a verified capability — under both conda and dpkg, CUDA appears in the package database only when the assets to actually compile and link (nvcc, cuda.h, libcudart) are present and located; partial installs warn and are omitted.
- A full tutorial (examples/step00–step09) plus a rewritten README, testing guide, and command-line/mode references.
Test runners & test infrastructure
- Self-discovering runners: Playwright + Vitest, then pytest + Catch2, then gtest.
- Runners contribute their own entry-point library (e.g. Catch2Main); compiled runner binaries/objects now depend on suite prerequisites.
- runners.info summary and per-runner info screens.
- Opt-in staged execution for interpreted drivers.
- New mjs language for node-based test drivers.
Package database (pkgdb)
- conda: discover packages by reading conda-meta records on disk — no agent invocation, and a $MAMBA_EXE/$CONDA_EXE→PATH resolver for the cases that still need the binary.
- conda CUDA: capability detection with the targets/ sysroot layout (validated on real hardware).
- dpkg CUDA: same capability, located via dpkg -L; handles both the NVIDIA apt-repo (/usr/local/cuda-X.Y/targets) and the distro nvidia-cuda-toolkit (/usr + multiarch) layouts.
- Catch2 detection added to the macports and dpkg databases.
- Create the staging directory before writing the database.
CLI / build paths
- Recursively-launched mm (e.g. the pkgdb rebuild) now forwards the command-line-set path traits (mode, bldroot, prefix, tag, environment, compilers, target), so mm --mode=… --bldroot=… delivers products to the right place instead of silently using defaults.
Web UX / Vite
- Vite pipeline for React/TS bundles: build/codegen/install/dev with a GraphQL knob (Relay example).
- Standalone pyre GraphQL server for the Relay example.
- vite-houdini example (houdini-react 2.0).
Build-system fixes
- make/extensions: fix module.main returning multiple files.
- make/compilers: suppress dependency-file generation when linking.
Documentation & examples
- New examples/step00–step09 tutorial: minimal C++ library → Python package → pybind11 extension → CLI driver → pyre as an external → pyre component/protocol pattern → shell session management.
- Rewritten README and tutorial; expanded FAQ (pyre, journal, session management); testing guide (per-file drivers and runners); mode table, mm.yaml guide, and command-line reference.
What's Changed
Full Changelog: v5.1.0...v5.2.0
Usability updates
Session environment management (--activate, --branch)
A new --activate flag emits shell export statements that wire the current build prefix into PATH and PYTHONPATH. --branch derives a tag from the repo name and current git branch, keys the build and install trees to it, and now subsumes --activate so a single invocation correctly sets the full environment. Re-activation is idempotent: mm_prefix and mm_pyc environment variables track what was previously injected so stale entries are removed before the new ones go in. --branch=false clears the tag and reactivates the default prefix. The --syntax flag controls sh/csh/fish output format, and bash and zsh completions were extended to cover all new flags.
Package database and platform modes
A new --mode flag selects the platform package manager: conda, macports, ubuntu/dpkg. Each mode has a package database builder that interrogates the local package manager and writes a pkg-{mode}.db file consumed by make/extern/. Conda support detects environment mismatches, guards against absent databases, and respects config.mm overrides. make/extern gained an extern.db.info diagnostic rule.
incpath/libpath traits replacing environment variables
MM_INCLUDES and MM_LIBPATH environment variables were replaced with proper pyre traits (incpath, libpath) so the values participate in the normal configuration cascade and can be set per-project in config files.
tag trait and build tree keying
A --tag flag exposes the build-tree tag directly as a configurable trait, seeded from the mm_tag environment variable. A depth asymmetry between bldroot and prefix was fixed at the same time.
C++ standard level predicates
All C++ compilers gained a function to extract the standard level from an asset's c++.flags, enabling make/languages predicates that compare the standard level against a threshold. Support for c++98 was retired.
flang Fortran compiler
flang is now supported as a Fortran compiler under the clang suite (make/compilers/clang/flang.mm), modeled after gfortran.
clean targets
Libraries, extensions, and packages now have clean logic to remove build products.
CUDA include path updates
make/extern/cuda was updated for CUDA 13's new include layout (CCCL paths added with wildcard guards).
mm.py deprecated
The old mm.py driver was moved to deprecated/.
What's Changed
- Add bash completion for mm by @rapa-mit in #29
- docs: add project documentation and fix inaccuracies by @rapa-mit in #30
- completion: add comprehensive target completion with all asset types by @rapa-mit in #31
- Add zsh completion for mm build system by @rapa-mit in #32
- Fix setting mpi.libraries for mpich flavor of MPI by @baagaard-usgs in #28
- make/extern added support for the new cuda include paths under cuda13 by @parosen in #24
- Improves control over the locations of the build assets by @aivazis in #34
New Contributors
- @rapa-mit made their first contribution in #29
- @baagaard-usgs made their first contribution in #28
- @parosen made their first contribution in #24
Full Changelog: v5.0.0...v5.1.0
Synchronize with the new driver version
The v5.0.0 driver is now stable and this release syncs the library version with it. It also contains a few enhancements in logging, compiler and external package support. See the change log for details
What's Changed
- make/extern: added support for kokkos library by @Tsilimidos in #19
- Added support for Intel MKL library by @Tsilimidos in #20
- main in #22
New Contributors
- @Tsilimidos made their first contribution in #19
Full Changelog: v4.5.0...v5.0.0
Maintenance release
Lots of little things plus rpath support so things build correctly on macos
What's Changed
- Major restructuring in anticipation of 5.0 by @aivazis in #14
- PR: Add support for {fmm3d} in mm by @trulko in #13
- Fixed building shared libraries and python extensions in macOS by @aivazis in #15
Full Changelog: v4.4.3...v4.5.0
The mm version now matches it's tag
v4.4.3 mm: bumped up the version
Bumped up to pyre 1.12.3
Full Changelog: v4.4.1...v4.4.2