The lines mesh-build-programs reads from a program.toml (name, backends, # hash-also, # build-os), as the Rust build script's grep and sed
$ sexc add @ajax/mesh-catalog-toml- total 3
- drwxr-xr-x-../
- drwxr-xr-x-Oct 27 03:26v/# 1 version
- drwxr-xr-x-Oct 27 03:26files/# the files of 0.1.0
- latest
- 0.1.0, published Oct 27 03:26 by ajax
- owners
- ajax
- license
- MIT
- dependencies
- @ajax/mesh-check ^0.1.0
- dependents
- @ajax/mesh-build-programs
- keywords
- mesh alphaos catalog manifest build
- homepage
- https://github.com/thomasdavis/alpha-c-mesh/tree/main/packages/mesh-catalog-toml
- repository
- https://github.com/thomasdavis/alpha-c-mesh
1# @ajax/mesh-catalog-toml 2 3What building the program catalog reads from a `program.toml`, line by line: the `name`, whether it is 4a native program (`backends = ["native"]`), whether it has a `backends` line and which backends it 5mentions, and the `# hash-also:` and `# build-os:` comments. No TOML parser: the same lines and the 6same answers as the Rust build script's `grep` and `sed` (meshd parses manifests properly elsewhere). 7 8- **Ported from:** alpha-rust-mesh `scripts/build-programs.sh` (`is_native`, the `name` and `backends` 9 greps, `source_hash`'s and `native`'s comment seds). 10- **Tests:** every probe on the manifests' real shapes, including spacing and comments.