Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
273 changes: 273 additions & 0 deletions .agents/docs/2026-11-22-test-round-wrap-up-plan.md

Large diffs are not rendered by default.

4 changes: 3 additions & 1 deletion .agents/docs/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -18,7 +18,7 @@ superseded_by: 2026-09-07-....md # when status is superseded
---
```

371 records.
372 records.

## By subject

Expand Down Expand Up @@ -135,6 +135,7 @@ Records that declare one. Everything else is listed by date below.

### plan

- [测试与 CI 一轮的收尾:平台列未命中的刷新条件(mcpp#996)、`i686-windows-msvc` 行、工作区索引与引号键的迁移、索引的全量验证](2026-11-22-test-round-wrap-up-plan.md) — active
- [Eight reports after 2026.9.27.1: implementation plan](2026-09-27-eight-reports-implementation-plan.md) — active
- [#690: implementation plan](2026-09-25-issue-690-implementation-plan.md) — landed
- [工具链选择与载荷可信度:实施计划](2026-09-24-toolchain-selection-implementation-plan.md) — landed
Expand Down Expand Up @@ -213,6 +214,7 @@ Records that declare one. Everything else is listed by date below.

### 2026-11

- [测试与 CI 一轮的收尾:平台列未命中的刷新条件(mcpp#996)、`i686-windows-msvc` 行、工作区索引与引号键的迁移、索引的全量验证](2026-11-22-test-round-wrap-up-plan.md) — active
- [包的特性作为机器可读的回答:一个目录项,两种来源,三种状态(mcpp#992)](2026-11-21-package-features-query-design.md) — active
- [离线、宿主输入与工具链的缺省:按内容取归档的来源、项目的取齐、宿主输入的声明、工具链的解析与锁、缺省版本的规则(mcpp#988、#989、#990)](2026-11-21-offline-host-inputs-and-toolchain-defaults-design.md) — active
- [构建程序的输入由观测给出:编译读到的文件、三道闸门的同一份记录、头文件的用法提示、提示的统一机制、契约中名字的歧义(mcpp#991、#852)](2026-11-21-build-program-observed-inputs-design.md) — active
Expand Down
36 changes: 35 additions & 1 deletion CHANGELOG.md
Original file line number Diff line number Diff line change
Expand Up @@ -4,7 +4,21 @@
> Each `## [<version>]` section is that release's notes. Entries are written in English
> from 2026.9.28.3 on; earlier entries remain as written.

## [Unreleased]
## [2026.11.22.1] - 2026-11-22

### Added

- `i686-windows-msvc`, the 32-bit x86 Microsoft ABI, is a `preview` row of the target table,
served by the msvc provider as `x86_64-windows-msvc` is; x86_64 Windows runs its programs
(WOW64). A project needs no `[target.i686-windows-msvc]` section to build it, and no platform is
looked up for it. `--target i686-windows` and `x86-windows-msvc` select it; before, they
selected no row. Under clang 23 its `import std` builds at C++20 only (docs/20) (mcpp#996).

### Changed

- The framework mcpp scaffolds tests with and suggests where a package has none is mtest 0.11.3
(`mtest gate` judges a ledger only for a set that runs every case; the library is
source-compatible with 0.11.2).

### Fixed

Expand All @@ -14,6 +28,26 @@
not yet filled is absent. Before, only the declared directories were judged, by existence,
so a reader beside a first fetch skipped the refresh and reported no local package index
(mcpp#927, design 2026-11-12 §18 P3).
- A request built without a platform refreshed the package index on every build more than the
debounce apart: a miss of the index's platform column refreshed for every row the engine does
not know and every `planned` one, and a custom triple a `[target.<triple>]` section defines, or
a `planned` row built with a named toolchain, is not refused for want of a platform (12 to 19 s
a build for `i686-windows-msvc` with a section). Only a request refused without a platform
refreshes now, judged by the facts the refusal reads; `platform = "none"` in a table ends the
lookup as `--platform none` does (SPEC-013 §14, mcpp#996).
- Two entries of a project's effective `[indices]` that name one location -- a member's beside
its workspace's `[workspace.indices]`, or two in one manifest -- registered the location twice,
and installing any package of it stopped at the provider as ambiguous, naming neither entry.
The build and `mcpp index update` refuse it now, naming both entries, the location and the
remedy (`index-location-named-twice`, SPEC-004 §9).
- An installed GCC's companions (binutils, the Linux headers) were read from the index's current
descriptor of the toolchain, not from the descriptor the payload was installed with. When xim's
gcc recipe moved binutils from 2.42.1 to 2.47, a gcc@16.1.0 installed beside binutils 2.42.1 was
given no binutils after `mcpp index update`, and its builds stopped at "cannot execute 'as'". The
installed descriptor is read first now, then the index's, and the first declaration the store
holds decides: a home that links the payload from an `[xlings] upstream` holds the companions
the index names, beside the upstream's descriptor (SPEC toolchain-management §2.9, design
2026-11-21 §3.5).
- `mcpp test` counts a suite run as a case by its cases on the program's line as the summary
does: an mtest program of one suite and seven cases read `8 cases` on its line and
`7 passed` in the summary.
Expand Down
1 change: 1 addition & 0 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -444,6 +444,7 @@ list` reports for this machine):
| `aarch64-linux-musl` | gcc 16, fully static — cross from x86_64 (qemu) or native | verified |
| `x86_64-windows-gnu` | gcc 16 MinGW-w64 — native on Windows, cross from Linux (wine) *(Windows default without Visual Studio)* | verified |
| `x86_64-windows-msvc` | `msvc@system` (detected VS/BuildTools) or llvm ¹ *(Windows default with Visual Studio)* | verified |
| `i686-windows-msvc` | `msvc@system` or llvm ¹ — 32-bit x86, run by WOW64 on x86_64 Windows | preview |
| `x86_64-windows-musl` | llvm 23 — a PE with a musl C library, which no gcc emits; the system comes from the dependency graph | preview |
| `aarch64-macos` | llvm *(macOS default)* | verified |
| `aarch64-macos-musl` · `x86_64-macos-musl` | llvm 23 — a Mach-O with a musl C library from the dependency graph, built on any host *(what `aarch64-macos` is off macOS)* | preview |
Expand Down
1 change: 1 addition & 0 deletions README.zh-CN.md
Original file line number Diff line number Diff line change
Expand Up @@ -393,6 +393,7 @@ mcpp 的身份模型有两条正交的轴:**工具链**是 `family@version`(
| `aarch64-linux-musl` | gcc 16,全静态;从 x86_64 交叉编译(qemu)或原生构建 | verified |
| `x86_64-windows-gnu` | gcc 16 MinGW-w64;Windows 上原生构建,Linux 上交叉编译(wine)(*无 Visual Studio 时的 Windows 默认*) | verified |
| `x86_64-windows-msvc` | `msvc@system`(探测 VS/BuildTools)或 llvm ¹(*有 Visual Studio 时的 Windows 默认*) | verified |
| `i686-windows-msvc` | `msvc@system` 或 llvm ¹;32 位 x86,在 x86_64 Windows 上由 WOW64 运行 | preview |
| `x86_64-windows-musl` | llvm 23;带 musl C 库的 PE,gcc 无法产出;系统部分由依赖图提供 | preview |
| `aarch64-macos` | llvm(*macOS 默认*) | verified |
| `aarch64-macos-musl` · `x86_64-macos-musl` | llvm 23;带 musl C 库的 Mach-O,系统部分由依赖图提供,任意宿主可构建(*非 macOS 宿主上的 `aarch64-macos`*) | preview |
Expand Down
2 changes: 1 addition & 1 deletion bench/mcpp.toml
Original file line number Diff line number Diff line change
Expand Up @@ -21,4 +21,4 @@ windows = "llvm@23.1.3"
# small fixture. `mcpp build` ignores [dev-dependencies], so the harness itself
# still takes nothing beyond `import std;`.
[dev-dependencies]
mcpplibs.mtest = "0.11.2"
mcpplibs.mtest = "0.11.3"
6 changes: 3 additions & 3 deletions docs/05-dependencies.md
Original file line number Diff line number Diff line change
Expand Up @@ -67,8 +67,8 @@ not deprecated:

```toml
[dev-dependencies]
mcpplibs.mtest = "0.11.2"
"mcpplibs.mtest.gtest" = "0.11.2"
mcpplibs.mtest = "0.11.3"
"mcpplibs.mtest.gtest" = "0.11.3"
```

```toml
Expand Down Expand Up @@ -483,7 +483,7 @@ refreshing it reads the local index at once, unless an index the home reads (the
provider's own, `xim`, or one the home declares) has no packages yet; it then
waits for that refresh and reads what it fetched, instead of reporting no local
package index *(2026.11.13.1+; the provider's own index and a directory not yet
filled, @NEXT@+, mcpp#927)*.
filled, 2026.11.22.1+, mcpp#927)*.

Run any command with `-v` to see the decision for each dependency and why.

Expand Down
9 changes: 9 additions & 0 deletions docs/07-workspace.md
Original file line number Diff line number Diff line change
Expand Up @@ -239,6 +239,15 @@ and a member reached as a dependency does not (mcpp 2026.10.11.1+; before that
release a member reached as a dependency received it and was refused for
stating an override).

`[workspace.indices]` merges with a member's `[indices]` by name, the member's
entry of a name first. When two entries of the result name one location (one
directory, or one repository at one pin), the build and `mcpp index update`
refuse it with `index-location-named-twice`: the location would be registered
twice, and each of its packages would be two candidates of one name. The remedy keeps one name: drop one entry, or, when one
of them is a workspace entry, state the index in the members that use it
instead *(2026.11.22.1+; before, the install failed as ambiguous and named neither
entry)*.

A conditional row counts as it evaluates for the target being built: a
`dialect_cxxflags` or `.abi` row for another target does not separate a member
from the others (§5.4), and one that holds is applied when the member is built
Expand Down
22 changes: 16 additions & 6 deletions docs/20-toolchains.md
Original file line number Diff line number Diff line change
Expand Up @@ -213,10 +213,18 @@ compared nor remembered.

A managed toolchain's companions -- the binutils GCC assembles and links with,
the Linux kernel headers of the glibc base, GCC's runtime libraries -- are the
versions its payload declares as runtime dependencies for this host. A store
that holds several versions answers with the declared one; without a
declaration, with the newest. A declared version the store does not hold is
reported as a degradation; `mcpp toolchain install` installs it again.
versions its payload declares as runtime dependencies for this host. Two
descriptors declare them, read in order: the one the payload was installed with,
which the installer keeps beside it, then the index's current one; the first
declaration the store holds decides *(2026.11.22.1+)*. An index update that moves the
declaration does not take the companions from an installed toolchain; before,
an installed GCC lost its binutils when xim's recipe moved to a version the
store did not hold. A home that links the payload from an `[xlings] upstream`
holds the companions the index names, beside the upstream's descriptor, and
takes those. A store that holds several versions answers with the declared one;
without a declaration, with the newest. Declarations the store holds none of
are reported as a degradation; `mcpp toolchain install` installs what they
name.

A project may state the binutils beside a GCC:

Expand Down Expand Up @@ -1648,8 +1656,10 @@ dialect_cxxflags = ["-D__cpp_impl_coroutine=201902L"]

In `cxxflags` the std module's precompile does not see it.

`i686-windows-msvc` is not a row of the target table; a project that builds
for it declares `[target.i686-windows-msvc]`, as for any custom triple.
`i686-windows-msvc` is a `preview` row of the target table *(2026.11.22.1+,
mcpp#996)*, served by the msvc provider as `x86_64-windows-msvc` is; x86_64
Windows runs its programs (WOW64). A project needs no `[target.i686-windows-msvc]`
section to build it. Before, it was a custom triple that required the section.

## Known Toolchain Limitation: GCC Modules Under a Non-ASCII Path (gcc 16)

Expand Down
4 changes: 3 additions & 1 deletion docs/21-the-target-triple.md
Original file line number Diff line number Diff line change
Expand Up @@ -106,7 +106,7 @@ what every `else` branch in the tree assumes. So the format is now one answer:
|---|---|
| `x86_64-linux-gnu`, `aarch64-linux-android`, `riscv64-none-elf`, `x86_64-openkal` | ELF |
| `aarch64-macos`, `aarch64-ios` | Mach-O |
| `x86_64-windows-gnu`, `x86_64-windows-msvc` | PE |
| `x86_64-windows-gnu`, `x86_64-windows-msvc`, `i686-windows-msvc` | PE |
| `wasm32-emscripten` | wasm |

It is **not** the same question as "is there an operating system to link
Expand Down Expand Up @@ -551,6 +551,7 @@ provider's runner ([41](41-devices.md)).
| `aarch64-windows-gnu` | preview | `llvm@23.1.3` | base | base | base | base |
| `x86_64-windows-musl` | preview | `llvm@23.1.3` | graph | graph | graph | payload |
| `x86_64-windows-msvc` | verified | — | — | — | — | system |
| `i686-windows-msvc` | preview | — | — | — | — | system |
| `aarch64-macos` | verified | — | — | — | SDK | — |
| `x86_64-macos` | planned | — | planned | planned | planned | planned |
| `aarch64-macos-musl` | preview | `llvm@23.1.3` | graph | graph | graph | graph |
Expand Down Expand Up @@ -599,6 +600,7 @@ vocabulary, nothing wired yet.
| `*-freebsd` | every host, through a platform | the rows are built-in; a platform names each identity's FreeBSD base package (`xim:x86_64-freebsd-sysroot`, `xim:aarch64-freebsd-sysroot`) and is selected with `[target.<row>] platform`, or by any selector the row meets (`[target.freebsd]`, `cfg(os = "freebsd")`); another platform package's provider does not compete with the chosen platform |
| `*-freebsd-musl` | every host, through the graph | openkal-platform's hosted part (0.28.0): openkal-musl over openkal-freebsd standalone, one static program; a request of `<arch>-freebsd` with no platform selected for it takes this identity (2026.11.10.2+), as `aarch64-macos` takes the musl identity on a host that is not a Mac |
| `x86_64-windows-msvc` | Windows | MSVC is located on the machine |
| `i686-windows-msvc` | Windows | the same; x86_64 Windows runs the programs (WOW64), and under clang 23 its `import std` builds at C++20 only ([20](20-toolchains.md)) |
| `x86_64-windows-musl` | Windows by payload; anywhere by graph | no gcc emits PE+musl, and LLVM cannot spell the triple |
| `aarch64-macos` | macOS | the SDK is the machine's |
| `*-none-elf` | every host | clang and lld are cross-compilers by construction |
Expand Down
8 changes: 8 additions & 0 deletions docs/35-platforms.md
Original file line number Diff line number Diff line change
Expand Up @@ -280,6 +280,14 @@ again. A refusal that follows says whether the index was refreshed, and why not.
Before, a row listed after the local copy was taken was refused as an unknown
target until `mcpp index update`.

A request that is built without a platform is not refused, so a miss of the
column for it does not refresh the index *(2026.11.22.1+, mcpp#996)*: a custom triple
a `[target.<triple>]` section defines, a `planned` row built with a named
toolchain (`[target.<row>] toolchain`, `--toolchain`), and a request a table
answers with `platform = "none"`, which ends the lookup as `--platform none`
does. The column is still read for the first two. Before, each such build more
than the debounce apart refreshed the index.

## Writing a platform package

A platform package is a package with a `[platform]` section. openkal-platform,
Expand Down
1 change: 1 addition & 0 deletions docs/50-machine-output.md
Original file line number Diff line number Diff line change
Expand Up @@ -676,6 +676,7 @@ a program classifying the outcome reads `reason`:
| `offline-download-required` | the run is offline and the plan needs a download: a toolchain, a package, a git revision or the package index; from 2026.11.21.1, with no archive directory named *(2026.9.16.1+)* |
| `artifact-unavailable-offline` | the run is offline, archive directories are named, and neither they nor the download cache hold an archive the plan needs; the message carries the provider's list *(2026.11.21.1+)* |
| `bundle-older-than-lock` | `mcpp fetch --from`: the bundle lacks a version `mcpp.lock` records *(2026.11.21.1+)* |
| `index-location-named-twice` | two entries of the effective `[indices]` (a manifest's, or a member's beside its workspace's) name one directory, or one repository at one pin; the message names both and the location *(2026.11.22.1+)* |
| `package-cycle` | the dependency graph contains a cycle of packages; the message names its edges *(2026.9.16.1+)* |
| `program-cxx-runtime-split` | a program or test that states a self-contained C++ runtime loads a C++ shared library of the build that couples to a shared one *(2026.9.16.1+)* |
| `static-package-in-two-images` | a static package several images of the build reach, on a target where an image cannot use another image's copy *(2026.9.16.1+)* |
Expand Down
8 changes: 7 additions & 1 deletion docs/specs/manifest-semantics.md
Original file line number Diff line number Diff line change
Expand Up @@ -5,7 +5,7 @@
| **规范编号** | SPEC-004 |
| **标题** | `mcpp.toml` 的平面划分、条件化形状、解析轴与命名规约 |
| **状态** | **草案(Draft)** |
| **版本** | 1.27 |
| **版本** | 1.28 |
| **最后修改** | 2026-11-21 |
| **最低实现版本** | 条件化形状:mcpp **2026.8.29.1**(`[target.<selector>.build-dependencies]` 起齐备);目标轴:mcpp **2026.9.6.4** |
| **作者/维护** | mcpp-community |
Expand Down Expand Up @@ -659,6 +659,11 @@ mcpp 2026.9.26.2,#703)。**
`[runtime]`,选择器的 `.build`、`.abi`、`.runtime`、`.targets`、`.dependencies`)不作用于
任何包,实现**必须**给出警告,`--strict` 下**必须**拒绝;同一张表在这样的根上同时写在根位置
与 `[workspace.X]` **必须**被拒绝。
合并之后,生效的 `[indices]` 中两项指向同一位置(规范化后的同一目录,或同一仓库的同一 pin)时,
该位置被向提供者登记两次,它的每个包成为同一名字的两个候选;登记索引的命令(构建与
`mcpp index update`)**必须**拒绝,只读索引文件的 `mcpp add` 不登记,不受此限。消息写出两项、该位置与修正,原因
token 为 `index-location-named-twice`(docs/50)。**已实现**(mcpp >= 2026.11.22.1;此前到提供者安装时
才以 ambiguous 失败,不指明两项)。
13. **按位置读取(兼容,自 mcpp 2026.10.10.1 弃用,自 mcpp 2027.1 移除;docs/51 的弃用登记表,
`workspace-position`)。** 工作空间根上没有 `[workspace.X]` 写法的 `[toolchain]`、
`[indices]`、`[profile.<name>]`、`[target.<triple>]` 标量行与 `[xlings]`、
Expand Down Expand Up @@ -953,3 +958,4 @@ mcpp 2026.10.10.1,#785、#786;第 14 至 16 条与第 13 条的依赖位置为 m
| 1.25 | 2026-11-21 | mcpp 2026.11.21.1(mcpp#990):§9 第 21 条 `[build] allow_host_tools`。 |
| 1.26 | 2026-11-21 | mcpp 2026.11.21.1(mcpp#990,设计 2026-11-21 离线与缺省 §3.2):§9 第 22 条 `[build] offline` 与第 23 条 `[xlings] archives`,两者按 §2 的四层取值,一次运行陈述为一个变量。 |
| 1.27 | 2026-11-21 | mcpp 2026.11.21.1(mcpp#992):新增 §16,特性的 `description`、一个目录项与查询回答的三种状态。 |
| 1.28 | 2026-11-22 | mcpp 2026.11.22.1(设计 2026-11-22 §6.2):§9 第 12 条,生效的 `[indices]` 中一个位置只有一个名字,两项指向同一位置时拒绝(`index-location-named-twice`)。 |
Loading
Loading