|
4 | 4 | > Each `## [<version>]` section is that release's notes. Entries are written in English |
5 | 5 | > from 2026.9.28.3 on; earlier entries remain as written. |
6 | 6 |
|
| 7 | +## [2026.10.30.1] - 2026-10-30 |
| 8 | + |
| 9 | +### Added |
| 10 | + |
| 11 | +- **The build's contract, `${mcpp.contract}`.** Every configuration writes |
| 12 | + `mcpp-contract.json` beside its compile database: the compiler of each |
| 13 | + language with the words every unit is compiled with (target, sysroot, |
| 14 | + target-side headers, platform and profile flags), and the link driver, its |
| 15 | + words and the archiver. A build program's action names it with |
| 16 | + `${mcpp.contract}` and reads it while ninja runs, so a foreign build system |
| 17 | + compiles for the target as the engine does; the engine's own C++ dialect and |
| 18 | + module words are not in it (e2e 982). mcpp-plugins 0.21.0's `deps-cmake` |
| 19 | + compiles a cross build's subproject from it. |
| 20 | +- **`[platform] runner.hosts`, carrier entries and `descriptor_keys`.** A |
| 21 | + platform states the `<os>-<arch>` pairs its runner exists for, any number of |
| 22 | + carrier entries each for the pairs in its `hosts` (an entry of a carrier |
| 23 | + model this mcpp does not build is skipped with a warning), and the |
| 24 | + descriptor blocks its targets read (SPEC-013 §1.1, §10, §11, §14). |
| 25 | +- **`runs_on` in `mcpp-package.json`.** Where a package runs is computed once |
| 26 | + when it is packed: `self`, the pairs it runs on with what it carries, and |
| 27 | + `with.<runner>`, the pairs it runs on given the machine's runner. |
| 28 | + |
| 29 | +### Changed |
| 30 | + |
| 31 | +- **A target reads the descriptor blocks its row names, never the build |
| 32 | + machine's (#851).** A target that is not Linux, macOS or Windows read the |
| 33 | + block of the system mcpp ran on, so a Web build took a dependency's `linux` |
| 34 | + block on Linux and its `windows` block on Windows, and an ok image the block |
| 35 | + of whichever system built it. Each row now names its blocks in order: |
| 36 | + `wasm32-emscripten` reads `emscripten`, then `linux`; `<arch>-openkal` |
| 37 | + `openkal`, then `linux` (a platform may state its own); iOS `ios`, then |
| 38 | + `macosx`; bare metal `none`. Version resolution, the synthesised manifest |
| 39 | + and the index refresh read the same block (unit `DescriptorKeys`). |
| 40 | +- **The Web link carries the profile's optimisation level (#851).** emcc runs |
| 41 | + wasm-opt and minifies the JavaScript launcher at the link, which had no |
| 42 | + `-O`: a release Web program was linked at `-O0`. The hello world's |
| 43 | + JavaScript is 13 KB rather than 66 KB (e2e 981). |
| 44 | +- **`[target.<sel>.abi] exceptions` takes the model (#851).** `"wasm"` selects |
| 45 | + WebAssembly's exception handling (`-fwasm-exceptions`), `"js"` the |
| 46 | + JavaScript model; `true` keeps the JavaScript model it has selected since |
| 47 | + 2026.9.12.3. The model is part of every cache key (e2e 981). |
| 48 | +- **`mcpp emit xpkg` names where a package runs (#860).** A |
| 49 | + self-contained universal package's entry named every system with every |
| 50 | + image architecture, so an Intel Mac installed a package that carries no |
| 51 | + runner for it. Each system's block names the architectures `runs_on` gives: |
| 52 | + the carried runners for a self-contained package, the pairs the platform's |
| 53 | + runner exists for otherwise. |
| 54 | + |
| 55 | +### Fixed |
| 56 | + |
| 57 | +- **A name two dependencies answer to is no package's (#852).** Two |
| 58 | + dependencies whose manifests both say `rules` warned on every build, and the |
| 59 | + bare name went to one of them. It is now published for neither: |
| 60 | + `MCPP_DEP_AMBIGUOUS_RULES` lists the qualified names, each qualified name |
| 61 | + keeps its own directory, and `dep_dir("rules")` ends the build program naming |
| 62 | + both (e2e 980). |
| 63 | +- **Programs start in the Android app sandbox again (#857).** Under `run-as` |
| 64 | + (SELinux `runas_app`) every program mcpp started failed with "not found" |
| 65 | + since 2026.10.26.2. A static strace showed one failing call, before any |
| 66 | + process was created: the root directory opened for reading, which the |
| 67 | + domain may search but not read. openkal-linux 0.18.3 opens every directory |
| 68 | + handle with `O_PATH`. |
| 69 | + |
7 | 70 | ## [2026.10.29.1] - 2026-10-29 |
8 | 71 |
|
9 | 72 | ### Fixed |
|
0 commit comments