|
1 | 1 | [package] |
2 | 2 | name = "plugins" |
3 | 3 | namespace = "mcpp" |
4 | | -version = "0.22.0" |
| 4 | +version = "0.22.1" |
5 | 5 | # The first mcpp release that speaks protocol 17 (SPEC-013, mcpp#847): the |
6 | 6 | # platform's directives `mcpp.plugins.platform` states (`link_driver`, |
7 | 7 | # `link_input`, `artifact_name`, `seal`, `run_host`), the `platform` phase, and |
@@ -98,9 +98,11 @@ sources = ["src/declare.cppm", "src/toolset.cppm", "src/fs.cppm", "src/tool.cppm |
98 | 98 | # The operating system of every member: the programs a member asks for a fact |
99 | 99 | # (`mcpp.plugins.tool::capture`), the libraries it opens and the platform it |
100 | 100 | # builds on, through mcpplibs.os. No unit includes a system header (0.21.0, |
101 | | -# docs/plugin-development.md §4). |
| 101 | +# docs/plugin-development.md §4). 0.4.4 (0.22.1) accepts openkal 0.24 and 0.25, |
| 102 | +# so a graph whose openkal is 0.25 (openkal-platform's version group) holds the |
| 103 | +# plugins; 0.4.0 named openkal 0.24.0 alone. |
102 | 104 | [feature-deps.plugins-core] |
103 | | -mcpplibs.os = "0.4.0" |
| 105 | +mcpplibs.os = "0.4.4" |
104 | 106 |
|
105 | 107 | # `mcpp.plugins.toolchain` -- the builders a root build program states its |
106 | 108 | # build toolchain with, in the toolchain phase of a project whose `[toolchain]` |
@@ -322,7 +324,7 @@ sources = ["src/progress.cppm", "src/progress_writer.cppm"] |
322 | 324 | # Since 0.3.1 a name in Windows' long spelling is the name it spells (the progress channel's path may |
323 | 325 | # be one). One release, the one mcpp's own modules name, so a build is the same at any later time. |
324 | 326 | [feature-deps.plugins-progress] |
325 | | -mcpplibs.os = "0.4.0" |
| 327 | +mcpplibs.os = "0.4.4" |
326 | 328 |
|
327 | 329 | [features.deps-cmake] |
328 | 330 | sources = ["deps/cmake.cppm"] |
|
0 commit comments