The vcpkg fixtures install under target/ and the criteria write their logs there: the fixtures live inside the package they depend on by path, whose host tool mcpp keys by a stamp of its tree (mcpp#705); the second build is planned on every host

Author: Sunrisepeak

.agents/docs/2026-09-26-deps-vcpkg-rules-qt-plan.md

@@ -1,6 +1,6 @@
 # 实施计划：`deps-vcpkg`、`rules-qt`、`deps-cmake` 的跨仓库交付
 
-状态：执行中 · 2026-09-26 · 设计见 `2026-09-26-deps-vcpkg-rules-qt-design.md`（第 4 版）。
+状态：执行中 · 2026-09-26（引擎下界 2026.9.26.2） · 设计见 `2026-09-26-deps-vcpkg-rules-qt-design.md`（第 4 版）。
 
 ## 1. 第 3 轮决定（设计第 4 版据此修改）
 
@@ -56,8 +56,16 @@ T1 mcpp#702 实现并发布（mcpp 侧）─────────┴──►
 
 | 任务 | 状态 |
 |---|---|
-| T0 设计第 4 版、本计划 | 进行中 |
-| T1 引擎 | 未开始 |
-| T2 xim 包 | Qt 归档 sha256 计算中 |
-| T3 插件 | 未开始 |
-| T4 / T5 | 未开始 |
+| T0 设计第 4 版、本计划 | 完成 |
+| T1 引擎 | mcpp#702 由 mcpp 侧合入，随 2026.9.26.2 发布 |
+| T2 xim 包 | xim-pkgindex#878、#879 已合入；`xlings-res/vcpkg` 双端资源已校验 |
+| T3 插件 | PR #29；Linux 各 fixture 在 2026.9.26.2 上通过；Windows、macOS 由 CI 验证 |
+| T3r / T4 / T5 | 等待 T3c |
+
+实测发现两项引擎缺口，均已报告：
+
+- 主机构建不读取主机三元组的 `[target.<triple>]` 段（mcpp#704），因此 Qt fixture 在 `[build]` 中声明
+  `cxx_runtime = "toolchain-coupled"`。
+- `path` 包的宿主工具以整棵目录树的 stamp 为键，嵌套其中的消费方写出的文件改变该键（mcpp#705）。fixture
+  位于插件仓库之内，因此其安装位于 `target/` 之下，检查脚本的日志写入 `target/ci/`，第二次构建以
+  `--profile dev` 绕过快路径，使 Linux 与 Windows、macOS 走同一条规划路径。从索引取得插件的项目不受影响。

.github/scripts/check-deps-and-qt.sh

@@ -38,7 +38,11 @@ assert_not_rerun() {
     mkdir -p target/ci
     touch -r "$stamp" target/ci/before-second-build
     sleep 1
-    "$MCPP" build > target/ci/second-build.log 2>&1 || { cat target/ci/second-build.log; fail "the second build failed"; }
+    # `--profile dev` names the default profile and declines mcpp's fast path,
+    # so the second build is planned on every host, as it is on Windows and
+    # macOS without the flag, and a host tool whose key moved is rebuilt.
+    "$MCPP" build --profile dev > target/ci/second-build.log 2>&1 ||
+        { cat target/ci/second-build.log; fail "the second build failed"; }
     [ -z "$(find "$stamp" -newer target/ci/before-second-build)" ] ||
         fail "the second build re-ran the installation ($stamp is newer)"
     echo "ok: a second build with nothing changed did not re-run the installation"
@@ -54,21 +58,21 @@ vcpkg_consumer() {
     "$MCPP" emit build-database --format json > target/ci/db.json 2> target/ci/emit.log ||
         { cat target/ci/emit.log; fail "emit build-database failed before any installation"; }
     grep -q 'vcpkg_installed' target/ci/db.json || fail "the database names no vcpkg_installed include directory"
-    [ ! -d vcpkg_installed ] || fail "emit build-database installed something"
+    [ ! -d target/vcpkg_installed ] || fail "emit build-database installed something"
     echo "ok: emit succeeded before the installation and named its include directory"
 
-    "$MCPP" build 2>&1 | tee build.log
-    "$MCPP" run | tee run.log
-    grep -qE '^vcpkg-consumer: fmt [0-9]+ says 42$' run.log || fail "the program did not print through fmt"
+    "$MCPP" build 2>&1 | tee target/ci/build.log
+    "$MCPP" run | tee target/ci/run.log
+    grep -qE '^vcpkg-consumer: fmt [0-9]+ says 42$' target/ci/run.log || fail "the program did not print through fmt"
     assert_not_rerun "$(stamp_of deps-vcpkg)"
 
     if is_windows; then
         # The pack collects it from the runtime search directory.
-        ls vcpkg_installed/x64-windows/bin/fmt.dll > /dev/null || fail "x64-windows built no fmt.dll"
-        run_directly vcpkg-consumer | tee direct.log
-        grep -qE '^vcpkg-consumer: fmt [0-9]+ says 42$' direct.log ||
+        ls target/vcpkg_installed/x64-windows/bin/fmt.dll > /dev/null || fail "x64-windows built no fmt.dll"
+        run_directly vcpkg-consumer | tee target/ci/direct.log
+        grep -qE '^vcpkg-consumer: fmt [0-9]+ says 42$' target/ci/direct.log ||
             fail "started from the build directory, the program did not find fmt.dll"
-        "$MCPP" pack --format dir | tee pack.log
+        "$MCPP" pack --format dir | tee target/ci/pack.log
         find target/dist -iname 'fmt.dll' | grep -q . || fail "the packed tree carries no fmt.dll"
         echo "ok: the packed tree carries fmt.dll"
     fi
@@ -77,11 +81,12 @@ vcpkg_consumer() {
 vcpkg_workspace() {
     cd "$ROOT/tests/vcpkg-workspace"
     rm -rf target app-a/target app-b/target vcpkg_installed
-    "$MCPP" build 2>&1 | tee build.log
-    "$MCPP" run -p app-a | tee run-a.log
-    "$MCPP" run -p app-b | tee run-b.log
-    grep -qE '^app-a: fmt [0-9]+$' run-a.log || fail "app-a did not run"
-    grep -qE '^app-b: fmt [0-9]+$' run-b.log || fail "app-b did not run"
+    mkdir -p target/ci
+    "$MCPP" build 2>&1 | tee target/ci/build.log
+    "$MCPP" run -p app-a | tee target/ci/run-a.log
+    "$MCPP" run -p app-b | tee target/ci/run-b.log
+    grep -qE '^app-a: fmt [0-9]+$' target/ci/run-a.log || fail "app-a did not run"
+    grep -qE '^app-b: fmt [0-9]+$' target/ci/run-b.log || fail "app-b did not run"
     # Each member builds into its own target/ and declares its own installation.
     [ "$(find . -path '*/target/*' -path '*deps-vcpkg*' -name '*.stamp' | wc -l)" -ge 2 ] ||
         fail "each member did not declare its own installation"
@@ -91,12 +96,17 @@ vcpkg_workspace() {
 cmake_consumer() {
     cd "$ROOT/tests/cmake-consumer"
     rm -rf target
-    "$MCPP" build 2>&1 | tee build.log
-    "$MCPP" run | tee run.log
-    grep -q '^cmake-consumer: greet says 42$' run.log || fail "the program did not call the subproject's library"
+    mkdir -p target/ci
+    "$MCPP" build 2>&1 | tee target/ci/build.log
+    "$MCPP" run | tee target/ci/run.log
+    grep -q '^cmake-consumer: greet says 42$' target/ci/run.log || fail "the program did not call the subproject's library"
     assert_not_rerun "$(stamp_of deps-cmake)"
+    # The builds after an edit are planned as well. The subproject lies inside
+    # this repository, the tree mcpp stamps for the plugins' host tool
+    # (mcpp#705), so an edit also rebuilds `mcpp-deps`; the build that is
+    # expected to re-run the installation absorbs that rebuild.
     touch greet/greet.c
-    "$MCPP" build > target/ci/third-build.log 2>&1 || { cat target/ci/third-build.log; fail "the rebuild failed"; }
+    "$MCPP" build --profile dev > target/ci/third-build.log 2>&1 || { cat target/ci/third-build.log; fail "the rebuild failed"; }
     # The installed library is the product of the rebuild, whatever the engine
     # does with the action's stamp.
     [ -n "$(find target -path '*deps-cmake*/install/*' -name '*greet*' -newer target/ci/before-second-build)" ] ||
@@ -112,7 +122,7 @@ cmake_consumer() {
     touch -r "$(stamp_of deps-cmake)" target/ci/before-added-file
     sleep 1
     echo added > greet/added.txt
-    "$MCPP" build > target/ci/added-build.log 2>&1 || { cat target/ci/added-build.log; fail "the build after adding a file failed"; }
+    "$MCPP" build --profile dev > target/ci/added-build.log 2>&1 || { cat target/ci/added-build.log; fail "the build after adding a file failed"; }
     [ -n "$(find "$(stamp_of deps-cmake)" -newer target/ci/before-added-file)" ] ||
         fail "a file added to the subproject did not re-run its installation"
     echo "ok: a file added to the subproject re-ran its installation"
@@ -121,9 +131,10 @@ cmake_consumer() {
 qt_consumer() {
     cd "$ROOT/tests/qt-consumer"
     rm -rf target
-    "$MCPP" build 2>&1 | tee build.log
-    "$MCPP" run | tee run.log
-    grep -qE "^qt-consumer: signal 42, resource 'greetings from rcc', translation 'hallo', Qt 6\." run.log ||
+    mkdir -p target/ci
+    "$MCPP" build 2>&1 | tee target/ci/build.log
+    "$MCPP" run | tee target/ci/run.log
+    grep -qE "^qt-consumer: signal 42, resource 'greetings from rcc', translation 'hallo', Qt 6\." target/ci/run.log ||
         fail "moc, rcc or lrelease did not reach the program"
     find target -name 'qt_consumer_de.qm' | grep -q . || fail "no .qm was produced"
     echo "ok: moc (header and inline), rcc and lrelease reached the program"
@@ -132,19 +143,20 @@ qt_consumer() {
 qt_widgets_consumer() {
     cd "$ROOT/tests/qt-widgets-consumer"
     rm -rf target
-    "$MCPP" build 2>&1 | tee build.log
-    QT_QPA_PLATFORM=offscreen "$MCPP" run | tee run.log
-    grep -q "^qt-widgets-consumer: platform offscreen, label 'made by uic'$" run.log ||
+    mkdir -p target/ci
+    "$MCPP" build 2>&1 | tee target/ci/build.log
+    QT_QPA_PLATFORM=offscreen "$MCPP" run | tee target/ci/run.log
+    grep -q "^qt-widgets-consumer: platform offscreen, label 'made by uic'$" target/ci/run.log ||
         fail "the platform plugin or the uic form did not reach the program"
     if is_macos; then
         find target -path '*/bin/platforms/libqoffscreen.dylib' | grep -q . ||
             fail "no platforms/libqoffscreen.dylib was deployed beside the program"
     fi
     if is_windows; then
-        QT_QPA_PLATFORM=offscreen run_directly qt-widgets-consumer | tee direct.log
-        grep -q "^qt-widgets-consumer: platform offscreen" direct.log ||
+        QT_QPA_PLATFORM=offscreen run_directly qt-widgets-consumer | tee target/ci/direct.log
+        grep -q "^qt-widgets-consumer: platform offscreen" target/ci/direct.log ||
             fail "started from the build directory, the program did not find the Qt DLLs"
-        "$MCPP" pack --format dir | tee pack.log
+        "$MCPP" pack --format dir | tee target/ci/pack.log
         find target/dist -iname 'Qt6Widgets.dll' | grep -q . || fail "the packed tree carries no Qt6Widgets.dll"
         find target/dist -ipath '*platforms/qoffscreen.dll' | grep -q . ||
             fail "the packed tree carries no platforms/qoffscreen.dll"

tests/vcpkg-consumer/build.mcpp

@@ -7,5 +7,11 @@ import mcpp.deps.vcpkg;
 int main() {
     mcpp::deps::vcpkg::options o;
     o.libraries = { "fmt" };
+    // This fixture lives inside the package it depends on by path, and mcpp keys
+    // that package's host tool by a stamp of its tree, `target/` excepted
+    // (mcpp#705). An installation beside the manifest would change the stamp,
+    // rebuild `mcpp-deps` and run again, so it goes under `target/`. A project
+    // that takes `mcpp:plugins` from the index keeps vcpkg's default.
+    o.install_root = "target/vcpkg_installed";
     return mcpp::deps::vcpkg::use(o) ? 0 : 1;
 }

tests/vcpkg-workspace/app-a/build.mcpp

@@ -6,5 +6,12 @@ import mcpp.deps.vcpkg;
 int main() {
     mcpp::deps::vcpkg::options o;
     o.libraries = { "fmt" };
+    // This fixture lives inside the package it depends on by path, and mcpp keys
+    // that package's host tool by a stamp of its tree, `target/` excepted
+    // (mcpp#705). An installation beside the manifest would change the stamp,
+    // rebuild `mcpp-deps` and run again, so it goes under the workspace's
+    // `target/`. A project that takes `mcpp:plugins` from the index keeps
+    // vcpkg's default.
+    o.install_root = "../target/vcpkg_installed";
     return mcpp::deps::vcpkg::use(o) ? 0 : 1;
 }

tests/vcpkg-workspace/app-b/build.mcpp

@@ -6,5 +6,12 @@ import mcpp.deps.vcpkg;
 int main() {
     mcpp::deps::vcpkg::options o;
     o.libraries = { "fmt" };
+    // This fixture lives inside the package it depends on by path, and mcpp keys
+    // that package's host tool by a stamp of its tree, `target/` excepted
+    // (mcpp#705). An installation beside the manifest would change the stamp,
+    // rebuild `mcpp-deps` and run again, so it goes under the workspace's
+    // `target/`. A project that takes `mcpp:plugins` from the index keeps
+    // vcpkg's default.
+    o.install_root = "../target/vcpkg_installed";
     return mcpp::deps::vcpkg::use(o) ? 0 : 1;
 }

tests/vcpkg-workspace/mcpp.toml

@@ -1,11 +1,12 @@
 # Fixture: two workspace members that link one vcpkg prefix and depend on
 # neither each other nor a common member.
 #
-# mcpp orders a `blocking` action before the compile edges of the package that
-# declares it and of no other, so each member declares the installation
-# itself. The two actions run the same `vcpkg install` against the root's one
-# manifest; `mcpp-deps` holds a lock on the installation root, so they run one
-# after the other and the second finds everything installed.
+# The compile edges of the package that declares a `prepare` action wait for
+# it, and those of no other package do, so each member declares the
+# installation itself. The two actions run the same `vcpkg install` against the
+# root's one manifest into one installation root; `mcpp-deps` holds a lock on
+# that root, so they run one after the other and the second finds everything
+# installed.
 [workspace]
 members = ["app-a", "app-b"]