Repository navigation
2026.11.17.1: deploy entries, license files in every pack, run files, the index's platform column, N48 - #944
Open
Sunrisepeak wants to merge 30 commits into
Open
Sunrisepeak wants to merge 30 commits into
Sunrisepeak wants to merge 30 commits into
Conversation
… and dist-web 0.20.0, a run's input files, the UEFI payload disk) and the layers of further target rows
…e, a run's inputs, the manifest's writing and part 1's remaining items (for review)
…inst the verification project
…e implementation plan with its review
… through their first pull request
A row states exe-suffix-fixed = true when its executable suffix is part
of loading its programs. A name template (a build program's
artifact_name, link.exe) then decides what precedes the suffix, and the
name ends in it once: artifact_name("exe", "{name}") gives app.js beside
app.wasm on wasm32-emscripten, where it gave a bare app, and {name}.js
gives app.js, not app.js.js. The built-in wasm32-emscripten row states
it; a platform states it for its own rows. The key is read by the
built-in table's generator and by the platform reader alike.
Spec: targets-and-providers v1.4 (2.1). Test: e2e web 1101.
…removed
[runtime] deploy takes a string, which is { from = <string> }, or a
{ from, to, name } table, in mcpp.toml and in descriptors. from may be a
glob of the engine's one dialect; a match lands under to at its path
below the glob's fixed directory (a literal path's is its parent, so
every existing entry lands where it did). name renames the one match.
A glob matching nothing and a name over several files are refused,
naming the package and the entry; a literal path may still be generated
by the build. deploy_files globs expand by the same rule.
The expansion runs when the build is planned and enters the graph;
placed.list beside build.ninja remembers the destinations, and a copy
the new graph no longer places is removed from beside the program.
SPEC-004 §15 (v1.20); docs/04 in both languages; unit tests for the
readers and expand_deploy_entry; e2e runtime/deploy 1102.
[package] license_files names a package's license and notice files as
globs relative to its root; a descriptor writes the same key in its
mcpp segment. Unset, the engine's default {LICENSE,LICENCE,COPYING,
NOTICE}* applies. The build plan records each package of the graph with
its patterns, and every pack, in every mode, stages them under
share/licenses/<package>/ with the role metadata: static libraries are
covered as shared ones are. A package for which nothing is found is
named in the report; a declared glob that selects nothing is warned
about.
This replaces collect_licenses, which ran only in self-contained packs,
under seven fixed names, and said nothing when it found none. That mode
still looks for the default files beside the shared objects it bundles
that no package declares, and names those without.
SPEC-004 §15.6-7, SPEC-014 §4.5.1 (v2.6); docs/04 and docs/10 in both
languages; unit tests for both readers; e2e pack/modes 1103.
…tory mcpp run --file FROM[=TO] (repeatable, dirun's spelling) and [test] files (the deploy entry grammar, with [target.'<sel>'.test] files) name the files a run finds in its working directory. With them, the program runs in run/<id>/ of the build tree, into which they are copied (never linked): mcpp run waits for the program and removes the directory; a test program's directory is shared by its split parts, removed when it passes, kept and named when it fails. The directory is prepared before the launch is composed, so --print-launch and a test's launch name a directory that holds the files. Without run files nothing changes. A runner receives them as run_files in MCPP_RUN_CLOSURE (schema 2) and in MCPP_RUNTIME_FILES beside the runtime files, which is now derived as the union: where the program has a file system of its own, its directory is its working directory. Both fast paths decline when run files are named. SPEC-002 §6.2 and §6.2.1 (v1.9), SPEC-017 B1.6 and B5 (2.4); docs/04, docs/08 and docs/09 in both languages; unit test for [test] files; e2e run/contract 1104 and test/selection 1105; 927 reads schema 2.
…the index lists
A platform package's index entry lists the rows it serves
(`platform_rows = { "x86_64-uefi", ... }`). Step 5 of the platform choice,
the target table's platform column, consults the index when the built-in
table has no answer: a row the engine does not know, a row a platform
defines, or a `planned` row. The package is selected as a series
(`<ns>.<name>@*`), so its release is chosen, locked and updated as any
platform series is, and the report names the source `index`.
- The project's own indices ([indices], .mcpp/) rank before the shared
ones; within one rank two claims are named and the first is taken.
- A row the table answers is unchanged, and every statement of the
project, the machine, the environment and the command line still comes
first.
- The entries are scanned once per command, and only for such a row
(about 0.05 s for the whole refusal over ~400 entries).
- mcpp 2026.11.16.1 reads an entry carrying the field and ignores it
(measured with openkal-platform's entry).
Tests: e2e 1106 (unknown row, planned row, the project first, two claims,
no column), PlatformSelect unit. SPEC-013 v1.11 (§3.1, §14, criterion 16),
docs/35 en/zh; the openkal-platform example uses multi-line inline tables.
…its host file for Windows too and names its copy apart from the original on case-insensitive file systems; the design record states the dirun test's cause as found
…hat holds the home's lock does not wait on another; the scan is cached per set of roots
…ider of that row here (x86_64-freebsd) takes the index's platform rather than a sibling row; table_answers decides it in both places
…e index answers; illumos and OpenBSD findings
…ost's own row is never among them
…its tests are, so a shared module is not compiled again over itself; a failure naming no step shows ninja's last lines (#945)
…s); the testing chapter says the programs are planned with the dev-dependencies
…o --print-target)
…ed; i686-openkal is the planned row a set's legs scan for
…o, so a request that ends mcpp leaves no run-<pid>-<n> behind
…e's C++ library leaves the link when another package supplies the C++ layer An OpenBSD sysroot holds only usr/ beside its mcpp.toml, and the payload resolution descended into usr/ as into an extracted tarball (payload_root, unit PmPayloadRoot). A NetBSD program built with libc++ from source (the provider's layers) still linked the base's libstdc++ through the base's ldflags (SPEC-002 §2.5, e2e 1108).
…D's import std through libc++ from source
This branch has not been deployed
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.
The engine's part of the ecosystem gap supplement, part 2 (design record
.agents/docs/2026-11-16-ecosystem-gap-supplement-part2-design.mdv6, part 1 for N43-N48), as one release. Each commit is a checkpoint with its tests, specs and docs.exe-suffix-fixed; a templated name keeps that suffix (app.json the Web row). Built-inwasm32-emscriptenstates it. targets-and-providers v1.4, e2e web 1101.[runtime] deployentries (ed15faa): a path or{ from, to, name },froma glob of the one dialect,tokeeps the tree below the glob's fixed directory,namerenames one file; no match or a name over several files is refused; copies no longer placed are removed. SPEC-004 §15 v1.20, e2e runtime/deploy 1102.[package] license_files(59bdfbe): everymcpp packstages each package's license files undershare/licenses/<package>/with the rolemetadata, default{LICENSE,LICENCE,COPYING,NOTICE}*; a package with none is named. SPEC-004 §15.6-7, SPEC-014 §4.5.1 v2.6, e2e pack 1103.mcpp run --file FROM[=TO]and[test] files; such a run works inrun/<id>/of the build tree (removed afterrunand after a passing test, kept and named after a failing one); runners receiverun_filesinMCPP_RUN_CLOSUREschema 2 and inMCPP_RUNTIME_FILES. SPEC-002 v1.9, SPEC-017 v2.4, e2e 1104, 1105.platform_rows); a row the built-in table has no platform for (unknown, platform-defined orplanned) takes that package as a series; the project's statements and its own indices come first; the report namesindex. mcpp 2026.11.16.1 ignores the field (measured). SPEC-013 v1.11, e2e 1106.mcpp.platforms.