Repository navigation
ninja 1.12.1-mcpp.1, mcpp.buildopt (BMI and object cutoff on every host, the private module fragment as a unit, the register), BSD rows off Linux hosts, workspace publishing - #949
Merged
Conversation
…kspace publishing (#947), and part 2's remaining items (for review)
… request per repository with checkpoint commits
…, with any zone abbreviation (#946 O1)
#945); a runner is taken on the hosts it states; a platform selected by a layer is warned of; the engine's default openkal-platform is 0.29.1; --strict names the key itself
…mat in a module of its own; a GCC BMI whose line maps alone moved is kept (bmi_cutoff, #946 O2) and a run states what changed (O6)
…ine maps; 1109: a runner is taken on the hosts it states
…y, --tag, the index's descriptor shape, --workspace and -p with SHA256SUMS (#947)
…ters 04, 11 and 50 in both languages, CHANGELOG
Sunrisepeak
marked this pull request as ready for review
November 17, 2026 04:55
…d-in by its dotted number
…host (O7, O5); a target that parses is ELF unless it says otherwise; the scan writes a file of its own
…platform 0.29 serves, the canary cell that passes
…; a private module fragment is built as a unit of its own
…ninja's update in one line
… carried dependencies first, feature defines by name (mcpp#945); an install says what it repaired
…the file as written, and a change of it selects the tests of its units
…hree passes on the real workspace
…s a file: the lib root, a feature's sources, the published interface (e2e 1117)
… created as; e2e 237 keeps what it writes in its own home
This was referenced Nov 17, 2026
Sunrisepeak
added a commit
that referenced
this pull request
Nov 18, 2026
…format); openkal-platform 0.29.2 is the default (#951) ## The defect The engine answered a row's object format and artifact names by a branch per system (`windows`, `macos`, `linux`, `openkal`, `emscripten`), and a built-in row without a branch took the host's naming. A platform's rows were read from data. On a Windows host a FreeBSD row's program was therefore `bin/<name>.exe` and its archives `.lib`, while the NetBSD and OpenBSD rows a platform package defines built there at once. Measured in mcpp-community/mcpp-platforms#4: with the FreeBSD sysroot's revision 2 the build of `x86_64-freebsd` finished on `windows-2025` and no `bin/hello` existed. 21 rows of the snapshot answered with the host's naming (FreeBSD, bare metal, iOS). It was not seen in #949 because e2e 1116, the case about this, carried the capability `llvm`, which is a Linux one: the case never ran on the two hosts it is about. ## The change One reading for every row, built-in or a platform's (SPEC-016 v1.5; design record §12): - `object-format`, `exe-suffix` and `shared-suffix` are read in three steps, the first statement taken: the row, its system (`[[platform.system]]`), the convention of the object format (elf, mach-o, pe, coff, wasm). The engine names no system for it, and the host's naming answers only for a triple that is neither a row nor of a system the table states. - `[[platform.system]]` accepts the three keys, in the built-in table and in a platform package alike. A `[[platform.define]]` row may leave `object-format` unstated: it is its system's, then ELF. - The built-in table states what the branches expressed: `pe` on the system `windows`, `mach-o` on `macos` and on the iOS rows, `.oke`/`.okso` on the ok image rows, `.js` on `wasm32-emscripten`. The rows snapshot is identical before and after that move, and the system-name baseline falls (linux 63→62, macos 51→49, windows 72→70, emscripten 18→17, ios 24→23). - `[email protected]` is the default platform of the rows openkal serves: it states the hosts of each runner, so `x86_64-windows-musl` on a Windows host runs with no runner without the project stating the release. ## Tests - `tests/unit/test_artifact_naming.cpp`: a FreeBSD row and a row of each format from a bogus host; row before system before format, over a platform's definitions; a triple of a stated system that is no row. - `tests/unit/test_platform.cpp`: the manifest reads the three system keys and a row without `object-format`. - e2e 1116 runs wherever the LLVM payload is (`scan-deps`), and holds the program to the row's exact name; it needs mcpplibs/mcpp-index#818 (the platform package's entry listed Linux hosts only). - e2e 1118: a platform's system states `exe-suffix`; a row that states none takes it, a row that states its own keeps it. ## With it The FreeBSD rows link on a Windows host with the sysroot packages' revision 2 (openxlings/xim-pkgindex#1184: zlib-compressed debug sections of the crt objects and static archives, which the lld of the Windows LLVM payload does not read, are held decompressed). No change of mcpp was needed for that. ## Compatibility Published platform packages were read row by row: their PE and COFF rows state `exe-suffix`, their ELF rows state none, and the three steps give them the names they had. Two readings differ for rows no published package has: a platform's PE row without `exe-suffix` is `.exe` (was no suffix), and a platform's row without `object-format` takes its system's before ELF. Version 2026.11.18.1; CHANGELOG, SPEC-016, docs/35 and the design record state the change.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
One round after 2026.11.17.1: mcpp#945, #946, #947, the items left by the second part of the ecosystem plan, and the build optimizations as one package. Design record:
.agents/docs/2026-11-17-ninja-cascade-publish-supplement-design.md(v5). Version 2026.11.17.2.ninja (mcpp#945)
1.12.1-mcpp.1(mcpp-community/ninja: 1.12.1 with the first commit of Invalidate Iterator in Plan::EdgeFinished ninja-build/ninja#2840, the correction of segfault inPlan::NodeFinishedninja-build/ninja#2662), installed through xlings beside the version a home has; an upgraded home is told which version replaces which, and keeps its ninja where the install fails.mcpp.buildopt (mcpp#946; SPEC-018, SPEC-019)
Everything mcpp does to a build beyond the compiler's and ninja's behaviour is one package,
modules/buildopt, and an entry of one register with its level, default and parameter. The pipeline asks at three seams (source, graph, edge).MCPP_BUILDOPT=offis the standard build.keep-bmi,keep-object,gcm-stamps,scan-passgcm-locations[profile.<name>] bmi_cutoff,MCPP_BMI_CUTOFFsplit-schedule[build] bmi_schedule,MCPP_BMI_SCHEDULEprivate-fragment[build] private_fragment,MCPP_PRIVATE_FRAGMENTTargets
x86_64-freebsd,-netbsd,-openbsdon macOS hosts,x86_64-freebsdon Windows hosts (e2e 1116). NetBSD and OpenBSD on Windows hosts need release: 2026.11.17.1 -- a link to a directory extracted on Windows is a directory link openxlings/xlings#719.registrylinked the shared home installed LLVM through the link; the shared home's 52 runtime links and clang's interpreter named the test home, and no compiler started once it was removed (three consecutive failures of a Linux unit shard). e2e 237 linked the shared home's.xlings.jsonand declared its own store in it; it now links what is read and copies what is written. A Linux unit shard that fails prints the home's runtime links, their generations and xlings' operations.[email protected]is the default.Publishing (mcpp#947)
mcpp publish --tag,--workspace,-p; archives and descriptors by identity; a sibling path edge takes the sibling's version;SHA256SUMS.Documents
SPEC-018 (the rebuild of modules), SPEC-019 (build optimizations), chapters 13 (code and project style) and 26 (build optimizations) in both languages,
modules/buildopt/README.md, chapters 04, 11 and 50, CHANGELOG.