Manifest reference

The program title on Roost. One to 64 characters. This is the listing title, not the calculator variable name, which comes from the built file.

The version this build publishes. At most 24 characters. No format is enforced, so 1.2.0, 2026.03 and beta-4 are all accepted, but pick one convention and keep it.

One line, shown in listings and search results. Truncated at 140 characters rather than rejected.

The long text on the program page. Truncated at 4000 characters. A TOML multi-line string is the comfortable way to write it.

Who to credit. Truncated at 64 characters.

One to four category keys. An unknown key fails the build. Some categories are restricted to administrators.

Up to twelve free-form tags, each at most 32 characters.

A hidden program is downloadable at its address but left out of listings, search and category counts.

Addresses of the libraries this build links against and that have to be on the calculator first. At most eight, each optionally pinned as address@version. See dependencies.

The shell command that produces the artifact. Run through bash -lc in the directory holding this manifest, as an unprivileged user, with no network. At most 512 characters.

For a libify library this key must be absent: Flight writes the command itself, and setting one is an error rather than a silent no-op.

Where the artifact lands, relative to the directory holding this manifest. A glob is allowed, but it has to match exactly one regular file. At most 200 characters.

Not read for a library: the appvar path comes from the library table instead.

Clone git submodules. They resolve over HTTPS only.

Wall clock for the build command. Between 30s and 30m. Go duration syntax, so 90s, 5m and 1m30s all parse.

Anything beginning with a slash.

Rejected outright, so a Windows-style path fails rather than being reinterpreted.

Any .. anywhere in the path, before or after cleaning.

Every manifest path reaches a shell, so quotes, backticks, dollar signs, semicolons, pipes, redirects and newlines are all refused.

The LibLoad name. One to eight characters, starting with a letter, capitals and digits only. This is what other programs link against and what LibLoad resolves at runtime.

Who builds it. libify lets CEagle generate the build command from the keys below; custom runs your own command and collects the files you name.

ce-libify and managed are accepted as spellings of libify; own and command as spellings of custom.

Public headers to ship in the developer archive. At most twelve. The archive is flat, so two headers whose base names collide are rejected.

The library version passed to ce-libify. Omitted when zero or absent.

The directory holding the C sources.

Where the headers live.

The export table. It is an ABI: see the export table.

The optimisation flag. Must start with -O and be at most eight characters.

Where your build leaves the appvar.

Where your build leaves the linker stub. An explicit empty string says the build ships none: the library still loads on the calculator, but nothing else can link against it.