mcpp-plugins

The build plugins the mcpp project maintains, published as one package, mcpp:plugins. mcpp is a general engine with a framework for build plugins; plugins come from this package, from third parties, or from the project itself, and build.mcpp is where a project uses them. A consumer selects the members it needs through features, imports each one from build.mcpp under the module name the member declares, and configures it there.

[build-dependencies.mcpp]
plugins = { version = "0.15.1", features = ["rules-spirv"], host-module = true }

// build.mcpp
import std;
import mcpp;
import mcpp.rules.spirv;

int main() {
    mcpp::rules::spirv::options opt;
    opt.includes = { "shaders" };
    return mcpp::rules::spirv::compile(opt) ? 0 : 1;
}

The edge is a [build-dependencies] entry, not a [dependencies] entry: host-module = true states which build-time product is wanted, and the section states that the package does not reach the target. A rule's library is never linked into the artifact (mcpp docs/05 §2.6.1).

The mcpp. prefix is reserved for this package. The full account of the families, and of how the engine routes a file to a rule, is in docs/engine-and-rules.md.

Some features add a sub-capability to a member: dist-apk-kotlin and dist-apk-maven (Kotlin sources, a Maven graph), and surface and deps, which the members imply. A feature states a mechanism and the tools that mechanism runs; the libraries and SDKs a program links are the project's declaration (0.15.0 removed rules-qt-xim*; see rules-qt).

mcpp.toml            the package: one feature per member
src/plugins.cppm     export module mcpp.plugins;  the version, mcpp::plugins::surface
                     (the declarations a consumer names) and mcpp::plugins::xml
rules/<x>.cppm       export module mcpp.rules.<x>;
tools/<x>.cppm       export module mcpp.tools.<x>;
dist/<x>.cppm        export module mcpp.dist.<x>;
deps/<x>.cppm        export module mcpp.deps.<x>;  deps/deps.cppm is shared
tests/<consumer>/    one project per member, built by CI with the pinned mcpp
docs/                one page per member or group of members

A member is one module file, one feature in mcpp.toml, a consumer under tests/ that CI builds and asserts on, a row in the table above with its mcpp floor, and a version bump. The conventions a member follows -- the same for a third-party or a project's own plugin -- are in docs/plugin-development.md; the division between what the engine owns and what the member owns is in docs/engine-and-rules.md.

A tag v<version> publishes the source archive; the index descriptor (mcpp-index/pkgs/m/mcpp.plugins.lua) names the GitHub archive and its GitCode mirror with one sha256.