0.13.0: deps-vcpkg, deps-cmake and rules-qt, written against mcpp's SPEC-007 (engine floor 2026.9.26.2) by speak-agent · Pull Request #29 · mcpp-community/mcpp-plugins

deps-vcpkg: a vcpkg manifest installed as a blocking action through mcpp-deps, and its prefix mapped into the build

Sunrisepeak

committed

106f904

deps-cmake: a CMake subproject configured, built and installed as one action, and its prefix mapped into the build

Sunrisepeak

committed

31b1991

rules-qt: moc, uic, rcc and lrelease as actions, the modules by full path, and the plugins beside the program; rules-qt-xim and rules-qt-xim-addons declare the SDK

Sunrisepeak

committed

9417bd9

0.13.0: the deps family and rules-qt in the manifest; every source-carrying member compiles on every host; CI measures the new members on three platforms

Sunrisepeak

committed

78f5476

0.13.0: the README states the deps family, deps-vcpkg, deps-cmake and rules-qt; the design record and the plan

Sunrisepeak

committed

fd927c4

CI builds against mcpp 2026.9.27.1, the release that carries runtime_library_dir and moves a check's stamp

Sunrisepeak

committed

4c297ce

0.13.0 needs no unreleased engine: the runtime is deployed beside the program on Windows and linked by name on Linux; measured on mcpp 2026.9.26.1

Sunrisepeak

committed

0b8deb7

0.13.0 follows mcpp's SPEC-007: installations are prepare actions with an output directory, prefixes are runtime search directories, and the build program never reads what an installation produces

Sunrisepeak

committed

5bff85b

Navigation Menu

Repository navigation

0.13.0: deps-vcpkg, deps-cmake and rules-qt, written against mcpp's SPEC-007 (engine floor 2026.9.26.2) - #29

0.13.0: deps-vcpkg, deps-cmake and rules-qt, written against mcpp's SPEC-007 (engine floor 2026.9.26.2)#29
speak-agent merged 13 commits into
mainfrom
feat/deps-vcpkg-rules-qt

Commits on Sep 25, 2026

deps-vcpkg: a vcpkg manifest installed as a blocking action through mcpp-deps, and its prefix mapped into the build

deps-cmake: a CMake subproject configured, built and installed as one action, and its prefix mapped into the build

rules-qt: moc, uic, rcc and lrelease as actions, the modules by full path, and the plugins beside the program; rules-qt-xim and rules-qt-xim-addons declare the SDK

0.13.0: the deps family and rules-qt in the manifest; every source-carrying member compiles on every host; CI measures the new members on three platforms

0.13.0: the README states the deps family, deps-vcpkg, deps-cmake and rules-qt; the design record and the plan

CI builds against mcpp 2026.9.27.1, the release that carries runtime_library_dir and moves a check's stamp

0.13.0 needs no unreleased engine: the runtime is deployed beside the program on Windows and linked by name on Linux; measured on mcpp 2026.9.26.1

0.13.0 follows mcpp's SPEC-007: installations are prepare actions with an output directory, prefixes are runtime search directories, and the build program never reads what an installation produces

Commits on Sep 26, 2026

Review: a file added to a subproject or an overlay re-runs the installation; uic, rcc and lrelease refuse two inputs with one output name; the Widgets fixture runs on macOS

The engine floor is 2026.9.26.2, the release that lands mcpp#702; lupdate's output directory outlives submit()

The Qt fixtures state cxx_runtime in [build]: mcpp reads a [target.<triple>] table only when a target is named, so a host build embedded a second libstdc++ and QtCore's RUNPATH found none

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…

Review: the Qt fixtures and README state what mcpp delivers for the runtime contract on each host (clang on the MSVC ABI links the static CRT); the installation stamp comes from a prepare action