Four ways in, and one thing the library deliberately does not offer.
mmgr_host is an interface target that links every module built at this machine's natural widths. There is one aggregate per environment, mmgr_host, mmgr_word32, mmgr_word16, mmgr_idx16, mmgr_checks, and linking one of the others is how you build your application against a narrower width without owning the hardware. See The environment matrix.
Turn the tests off in a consuming build:
Two roots: include/ carries the umbrella header, src/ carries the modules. Both come with the CMake target. A consumer adds neither by hand.
The path is part of the interface: the generated reference prints the include line for every entity for that reason.
library.json sets srcDir to src, unflags -std=gnu99 and adds -std=gnu11, and so the C11 requirement is carried by the manifest and not by your build file.
Download the repository as a zip and use Sketch → Include Library → Add .ZIP Library, or clone it into your libraries/ directory. library.properties declares it, and keywords.txt gives the editor the module stems so spat and scrut highlight.
Every knob is a preprocessor define with a default, and so you set only what you are changing:
Sizes are not among them. A pool states its own extent at its declaration, and so there is no build knob that sizes one.
Every compile-time knob lists all of them.
There is no install(), no export(), no MMgrConfig.cmake and no find_package support, and by design, and complete.
The ABI is a function of the compile-time widths. A libmmgr.a built at EMBED_WORD_BITS=64 and a consumer compiled at EMBED_WORD_BITS=32 disagree about the size of embed_word, therefore about the layout of every struct containing one, therefore about every offset the library computes, and nothing in the link would catch it. embed_types.h is full of static asserts to police exactly this class of mistake, and they only fire when the library and its consumer are compiled together.
Shipping a binary would make that mismatch possible while making it invisible. Consuming the source makes it impossible. That is the trade, and for a library this size, twenty small modules, no external dependencies, compiling it into your build costs almost nothing.
If you need a prebuilt artifact anyway, build the aggregate you want and vendor it together with the exact width definitions it was built against. Do not ship one without the other.
