Repository navigation
Commit 424385e
authored
2026.11.17.1: deploy entries, license files in every pack, run files, the index's platform column, N48 (#944)
* design record: N43-N47 (UEFI Shell arguments, the DOS first stack, N9 and dist-web 0.20.0, a run's input files, the UEFI payload disk) and the layers of further target rows
* design record: ecosystem gap supplement, part 2 -- the roles of a file, a run's inputs, the manifest's writing and part 1's remaining items (for review)
* Design record: part 2 revised after a multi-angle review (v2)
* Design record: part 2 v3, the decided points and a two-way review against the verification project
* Design record: part 2 v4, N48, the FreeBSD runner, setup-mcpp, and the implementation plan with its review
* Design record: part 2 v4, mark the settled sections
* Design record: part 2 v5, the plan is settled and new repositories go through their first pull request
* N48: a row's fixed executable suffix ends a templated name
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.
* deploy: an entry is a path or a table; globs, name, and stale copies 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.
* license_files: every pack stages each package's license files
[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.
* run files: mcpp run --file, [test] files, and the run's working directory
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.
* platform: a row the built-in table has no platform for takes the one 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.
* docs: multi-line inline tables are 2026.11.17.1+, and the changelog says so (#929)
* Design record: part 2 v6, measurements and the decisions taken while implementing
* 2026.11.17.1: the version and the changelog's section
* Design record: part 2 is active; the .agents/docs index; the dirun test's cause
* platform: a manifest's [[platform.system]] reaches the platform reader
* tests: 1104's runner is declared for the host's own row; 1105 states 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
* platform: the index's column is scanned with no lock held, so a leg that holds the home's lock does not wait on another; the scan is cached per set of roots
* skills: a pull request that needs the full CI is labelled ci:full before its push
* platform: a row the table holds with no platform and no built-in provider of that row here (x86_64-freebsd) takes the index's platform rather than a sibling row; table_answers decides it in both places
* Design record: the timeouts' cause is open; the fourth kind of row the index answers; illumos and OpenBSD findings
* SPEC-013 §14: which rows an entry's platform_rows lists, and that a host's own row is never among them
* test: a package's programs are planned with its dev-dependencies, as its tests are, so a shared module is not compiled again over itself; a failure naming no step shows ninja's last lines (#945)
* test: the programs a test runs request no [test] features (#941 stands); the testing chapter says the programs are planned with the dev-dependencies
* tests: 1104 takes the host's row from its build directory (mcpp has no --print-target)
* Design record: the timeouts did not recur with the scan's lock released; i686-openkal is the planned row a set's legs scan for
* run files: the run's directory is removed by the interrupt watcher too, so a request that ends mcpp leaves no run-<pid>-<n> behind
* Bases: a version directory with a manifest is the package root; a base'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).
* Design record: the OpenBSD package root, the image profile, and NetBSD's import std through libc++ from source
* A cfg selector names the platform of a row only that platform defines
The early selection read only tables keyed by the triple, so
[target.'cfg(any(os = "netbsd", os = "openbsd"))'] platform was refused as
an unknown target. Until a row defines the triple, a selector is answered by
its words, <arch>-<os>[-<env>] (SPEC-013 §3.1, e2e 1040).
* runner = true | false: an override's consent alone, { enabled = ... }; the refusal names it and the platform-wide selector
A runner's statement (a platform's, a provider's) states its command; an
override table may enable or disable it by a boolean (e2e 1092 G, H).
* Revert the programs planned with the dev-dependencies (#945): a dev-dependency's objects reached the programs' link
CI showed the change wrong: a dev-dependency that supplies main (gtest_main)
was linked into the program (duplicate symbol main, e2e graph/78), and the
programs' plan no longer matched mcpp build's, so the test fast path declined
(e2e 1069). The programs are planned as mcpp build plans them, as before. The
diagnostic for a failure that names no step stays.
* Docs: runner = true | false, and a runner's statement and its consent as two layers (SPEC-013 §10, docs/41, docs/04)
* Matrix: i686-linux-musl and i686-openkal are named a platform by the index's column (measured on all four hosts)
* A test plan that configures a package otherwise than mcpp build builds in a directory of its own; a build program's unchanged output keeps its time (#945)
The tests' configuration axis (#test=) enters the fingerprint when the tests
ask a package for features ([test] features, or a dev-dependency entry that
asks a package the manifest also depends on). One directory held both
configurations, whose interfaces and objects are named by module and
package, and each plan compiled over the other. A build program rerun when
its cached answer was another configuration's rewrote its generated source
with a new time. e2e 1107: one compile per configuration, none again.1 parent dcc96e5 commit 424385e
68 files changed
Lines changed: 3233 additions & 246 deletions
File tree
- .agents
- docs
- skills
- mcpp-contributing
- mcpp-release
- docs
- specs
- zh
- modules
- manifest/src
- toolchain-model
- data
- src
- versioning/src
- src
- build
- prepare
- cli
- pack
- platform
- pm
- tests
- e2e
- openkal
- pack
- runtime
- run
- test
- web
- matrix
- unit
Some content is hidden
Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
57 | 57 | | |
58 | 58 | | |
59 | 59 | | |
| 60 | + | |
| 61 | + | |
| 62 | + | |
| 63 | + | |
| 64 | + | |
60 | 65 | | |
61 | 66 | | |
62 | 67 | | |
| |||
721 | 726 | | |
722 | 727 | | |
723 | 728 | | |
| 729 | + | |
| 730 | + | |
| 731 | + | |
| 732 | + | |
| 733 | + | |
| 734 | + | |
| 735 | + | |
| 736 | + | |
| 737 | + | |
| 738 | + | |
| 739 | + | |
| 740 | + | |
| 741 | + | |
| 742 | + | |
| 743 | + | |
| 744 | + | |
| 745 | + | |
| 746 | + | |
| 747 | + | |
| 748 | + | |
| 749 | + | |
| 750 | + | |
| 751 | + | |
| 752 | + | |
| 753 | + | |
| 754 | + | |
| 755 | + | |
| 756 | + | |
| 757 | + | |
| 758 | + | |
| 759 | + | |
| 760 | + | |
| 761 | + | |
| 762 | + | |
| 763 | + | |
| 764 | + | |
| 765 | + | |
| 766 | + | |
| 767 | + | |
| 768 | + | |
| 769 | + | |
| 770 | + | |
| 771 | + | |
| 772 | + | |
| 773 | + | |
| 774 | + | |
| 775 | + | |
| 776 | + | |
| 777 | + | |
| 778 | + | |
| 779 | + | |
| 780 | + | |
| 781 | + | |
| 782 | + | |
| 783 | + | |
| 784 | + | |
| 785 | + | |
| 786 | + | |
| 787 | + | |
| 788 | + | |
| 789 | + | |
| 790 | + | |
| 791 | + | |
| 792 | + | |
| 793 | + | |
| 794 | + | |
| 795 | + | |
| 796 | + | |
| 797 | + | |
0 commit comments