feat(build): build.mcpp 补全 — 环境契约 + cross 下运行 + 依赖包执行 (0.0.95) (#222)

G3+G2:MCPP_* 环境契约无条件入重跑键、cross 下宿主链解析真跑、依赖包 build.mcpp(Cargo 作用域,产物项目本地化,registry 零写入);版本 bump 0.0.95;e2e 110–112

Author: Sunrisepeak

docs/07-build-mcpp.md

@@ -92,6 +92,37 @@ If your `build.mcpp` also needs to *write* a generated file, mix in a textual
 stdout protocol above remains the low-level substrate; `import mcpp;` is the typed
 layer over it.
 
+## Environment contract (mcpp 0.0.95+)
+
+The running program receives the build context as `MCPP_*` variables
+(Cargo's env-family equivalent), also exposed through typed readers:
+
+| Variable | Typed reader | Value |
+|---|---|---|
+| `MCPP_TARGET` | `mcpp::target()` | resolved canonical triple (the `--target` triple under cross; the host triple natively) |
+| `MCPP_HOST` | `mcpp::host()` | the host triple |
+| `MCPP_PROFILE` | `mcpp::profile()` | effective profile name (`dev`/`release`/…) |
+| `MCPP_OUT_DIR` | `mcpp::out_dir()` | a writable scratch/output dir owned by mcpp |
+| `MCPP_MANIFEST_DIR` | `mcpp::manifest_dir()` | the package root (= CWD) |
+| `MCPP_FEATURE_<NAME>` | `mcpp::has_feature("name")` | set to `1` per active feature (same `<NAME>` sanitization as the `MCPP_FEATURE_` compile macro) |
+| `MCPP_FEATURES` | — | comma-separated active feature list |
+
+These values are folded into the re-run key **unconditionally** — changing the
+target, profile, or feature set re-runs the program without any
+`rerun-if-env-changed` declaration.
+
+## Dependencies' build.mcpp (mcpp 0.0.95+)
+
+A dependency that ships a `build.mcpp` gets it compiled and run too (the
+Cargo `build.rs` model — building a package means trusting its build program),
+after its features are resolved and before the source scan. Scope follows
+Cargo: `cxxflag`/`cflag`/`cfg` directives color **only that package's own
+TUs**; `link-lib`/`link-search` reach the final link. Its artifacts (binary,
+cache, `MCPP_OUT_DIR`) live in the **consuming project's**
+`target/.build-mcpp/deps/<pkg>@<ver>/` — a registry package root is shared
+across projects (and may be read-only), so it is never written to; relative
+`generated=` paths resolve against `MCPP_OUT_DIR`, not the package root.
+
 ## Incremental: declared inputs (no needless re-runs)
 
 mcpp does **not** re-run `build.mcpp` on every build. It caches the program's
@@ -113,11 +144,11 @@ When nothing changed you'll see `build.mcpp up to date (cached)`; otherwise
 
 ## Notes & limits
 
-- **Runs on the host.** `build.mcpp` compiles and runs with the host toolchain.
-  Under a cross build (`mcpp build --target <triple>`) it is **skipped with a
-  warning** for now (host-toolchain-for-cross is a planned follow-up). Gate
-  *dependencies* on the target with `[target.'cfg(...)']` tables instead — those
-  evaluate on the resolved target. See [05 - mcpp.toml Manifest Guide](05-mcpp-toml.md).
+- **Runs on the host — including under cross** (mcpp 0.0.95+). Under
+  `mcpp build --target <triple>` the program is compiled with a host-resolved
+  toolchain, runs on the host, and sees `MCPP_TARGET` = the cross triple.
+  For purely declarative target gating, `[target.'cfg(...)']` tables remain
+  the first choice — see [05 - mcpp.toml Manifest Guide](05-mcpp-toml.md).
 - **CWD is the project root**, so relative paths (`src/generated.cpp`) land where
   you expect.
 - A non-zero exit from `build.mcpp` aborts the build and prints its output.

docs/zh/07-build-mcpp.md

@@ -86,6 +86,33 @@ int main() {
 只有 `import std;` 是不必要的。上面的裸 stdout 协议仍是底层基底;`import mcpp;` 是其上的
 类型化层。
 
+## 环境契约(mcpp 0.0.95+)
+
+运行中的程序以 `MCPP_*` 环境变量得到构建上下文(对应 Cargo 的环境变量族),
+也有类型化读取端:
+
+| 变量 | 类型化读取 | 值 |
+|---|---|---|
+| `MCPP_TARGET` | `mcpp::target()` | 解析后的 canonical 三元组(交叉构建下是 `--target` 三元组,原生构建是宿主) |
+| `MCPP_HOST` | `mcpp::host()` | 宿主三元组 |
+| `MCPP_PROFILE` | `mcpp::profile()` | 生效 profile 名(`dev`/`release`/…) |
+| `MCPP_OUT_DIR` | `mcpp::out_dir()` | mcpp 提供的可写输出/暂存目录 |
+| `MCPP_MANIFEST_DIR` | `mcpp::manifest_dir()` | 包根(= CWD) |
+| `MCPP_FEATURE_<NAME>` | `mcpp::has_feature("name")` | 每个活跃 feature 置 `1`(`<NAME>` 消毒规则与 `MCPP_FEATURE_` 编译宏一致) |
+| `MCPP_FEATURES` | — | 活跃 feature 逗号列表 |
+
+这些契约值**无条件**折入重跑键——换 target、换 profile、开关 feature 都会触发重跑,
+不需要任何 `rerun-if-env-changed` 声明。
+
+## 依赖包的 build.mcpp(mcpp 0.0.95+)
+
+带 `build.mcpp` 的依赖包也会被编译并运行(Cargo `build.rs` 模型——构建一个包
+即信任其构建程序),时机在其 feature 解析之后、源扫描之前。作用域照 Cargo:
+`cxxflag`/`cflag`/`cfg` 指令只染色**该包自身的 TU**;`link-lib`/`link-search`
+到达终链。其产物(二进制、缓存、`MCPP_OUT_DIR`)放在**消费方工程**的
+`target/.build-mcpp/deps/<pkg>@<ver>/` 下——registry 包根跨工程共享(且可能只读),
+绝不写入;相对 `generated=` 路径按 `MCPP_OUT_DIR` 解析,而非包根。
+
 ## 增量:声明输入(避免无谓重跑)
 
 mcpp **不会**每次构建都重跑 `build.mcpp`。它会缓存程序产出的指令,只有当它依赖的东西
@@ -106,9 +133,9 @@ mcpp **不会**每次构建都重跑 `build.mcpp`。它会缓存程序产出的
 
 ## 说明与限制
 
-- **在主机上运行。** `build.mcpp` 用主机工具链编译并运行。在交叉构建
-  (`mcpp build --target <triple>`)下目前会**跳过并给出警告**(主机工具链交叉是计划中的
-  后续项)。要按目标平台门控*依赖*,请改用 `[target.'cfg(...)']` 表——它们按解析后的目标
-  求值。参见 [05 - mcpp.toml 工程文件指南](05-mcpp-toml.md)。
+- **在主机上运行——交叉构建下也是**(mcpp 0.0.95+)。`mcpp build --target <triple>`
+  下,程序用宿主解析的工具链编译、在宿主运行,并看到 `MCPP_TARGET` = 交叉三元组。
+  纯声明式的目标门控仍首选 `[target.'cfg(...)']` 表——参见
+  [05 - mcpp.toml 工程文件指南](05-mcpp-toml.md)。
 - **当前工作目录是工程根目录**,因此相对路径(`src/generated.cpp`)会落在你预期的位置。
 - `build.mcpp` 非零退出会中止构建并打印其输出。

mcpp.toml

@@ -1,6 +1,6 @@
 [package]
 name        = "mcpp"
-version     = "0.0.94"
+version     = "0.0.95"
 description = "Modern C++ build & package management tool"
 license     = "Apache-2.0"
 authors     = ["mcpp-community"]