|
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.11.2.1] - 2026-11-02 |
| 8 | + |
| 9 | +A dependency's source is used without being copied: a dependency edge carries |
| 10 | +patches, and a dependency is compiled into its consumer (design 2026-11-02, |
| 11 | +part 3 §14). With them, mcpp#875 and mcpp#881. |
| 12 | + |
| 13 | +### Added |
| 14 | + |
| 15 | +- **`patches = [...]` on a dependency edge** (docs/05). Unified diffs, named |
| 16 | + relative to the declaring manifest, applied in order to the verified source by |
| 17 | + mcpp's own exact applier (no fuzz, no search, no conversion of line endings; |
| 18 | + one leading directory of each path removed; renames, copies and binary changes |
| 19 | + refused). A patched library is another library, a variant: its identity is |
| 20 | + (package, version, patch set), its source a tree of its own under the mcpp |
| 21 | + home (`cache/src/<package>/<version>+p<digest>`), and its build, BMIs and |
| 22 | + cache entries its own. Version and git dependencies; a `path` dependency with |
| 23 | + patches is refused. `mcpp.lock` records the variant and each patch's path and |
| 24 | + SHA-256 (`variant`, `patches`); `mcpp emit sbom` states them as the component's |
| 25 | + pedigree. A variant's tree is collected by `cache gc`, `prune` and after a |
| 26 | + build as the cache's entries are. e2e 1001. |
| 27 | +- **`embed = true` and `exclude = [...]` on a dependency edge** (docs/05). The |
| 28 | + dependency's sources, less `exclude`, are compiled into the consumer with the |
| 29 | + consumer's flags and, for those files, the dependency's include directories |
| 30 | + and compile flags; the dependency builds nothing of its own in that |
| 31 | + configuration, and a program that reaches it without its embedder is refused |
| 32 | + naming both. `exclude` without `embed` is refused at the manifest. e2e 1002. |
| 33 | +- **One program, one variant of a package**: two programs of one configuration |
| 34 | + may each use their own patch set; a program that reaches two variants of a |
| 35 | + package, or a variant and the package without patches, is refused naming |
| 36 | + them. e2e 1003. |
| 37 | + |
| 38 | +### Fixed |
| 39 | + |
| 40 | +- **A build with a toolchain outside every provider found no ninja** (mcpp#875): |
| 41 | + the ninja mcpp installed into its own home is used after the one beside the |
| 42 | + compiler's provider and before PATH, and `MCPP_NINJA` names the same one. With |
| 43 | + none, the build is refused naming where it looked, instead of "cannot start |
| 44 | + 'ninja'". e2e 1004. |
| 45 | +- **`clean --stale` said every directory was current after keeping one** |
| 46 | + (mcpp#881): directories kept for being newer than the window are counted, and |
| 47 | + the summary says how many and within what window. The default window of |
| 48 | + `--older-than` is `[build] keep_days` (3 days), the window of the sweep after a |
| 49 | + build, instead of one day. The SubOS remedies name the home: |
| 50 | + `XLINGS_HOME=<registry> xlings self doctor --fix`. e2e 1005. |
| 51 | + |
| 52 | +### Design |
| 53 | + |
| 54 | +- Design 2026-11-02 part 3 (ok image performance parity), approved; part 2 |
| 55 | + rev 11 and 12 corrections. |
| 56 | + |
7 | 57 | ## [2026.10.31.3] - 2026-10-31 |
8 | 58 |
|
9 | 59 | A large workspace keeps its bytes once and builds each output once (mcpp#874; |
@@ -2906,7 +2956,7 @@ C 库来自依赖图的链接此前没有 `--sysroot`,clang 会从宿主推导 ` |
2906 | 2956 |
|
2907 | 2957 | ### 成员清单只有一种读法 |
2908 | 2958 |
|
2909 | | -`mcpp publish`、`mcpp pack`、`mcpp emit xpkg`、`mcpp toolchain list`、`mcpp sbom`、`mcpp index list`/`update`、 |
| 2959 | +`mcpp publish`、`mcpp pack`、`mcpp emit xpkg`、`mcpp toolchain list`、`mcpp emit sbom`、`mcpp index list`/`update`、 |
2910 | 2960 | `mcpp update` 的索引刷新、快路径的身份判定与测试发现,此前直接读取成员目录中的原始清单:省略 |
2911 | 2961 | `version` 的成员被拒绝,未写 `[toolchain]` 的成员在 `toolchain list` 中显示全局默认工具链,而同一 |
2912 | 2962 | 目录下的 `mcpp build` 用的是工作空间的工具链。现在它们与 `prepare_build` 经同一个函数读取继承后的 |
|
0 commit comments