| Filename | Latest commit message | Latest commit date |
|---|---|---|
Jorijn van der Graaf
84d9d66649
All checks were successful
Flatpak / flatpak (pull_request) Successful in 7m27s
The README suggested giving one sibling a list without a flag only the project reads, so that the sibling would not get a build directory of its own. When another path loads the same sibling with the full list, that filter is what gives it the second directory: two builds of one project, both in the program (#41). It now says to build such a list once and give it to every sibling. It also says the default is read when the spec is made, so a spec made at namespace scope, on another thread or in a script forwards nothing, and that cfg.projectArgs, the part ApplyStandardArgs did not interpret, is no substitute: it drops the target and the build type. The comments on ProjectArgs() and on Configuration::projectArgs say the same. The spec comment named --local as a flag the default carries down a chain of siblings. Through a GitProject hop it breaks: the clone has no checkouts beside it. The GitProject comment said the clone is keyed by the args; only the Configuration is, and every arg list builds in the one clone. AGENTS.md now notes that a stale harness gives no symptom for a changed default member initialiser: project.cpp silently gets the old default. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> |
||
| .. | ||
| Crafter.Build-Asset.cppm | ||
| Crafter.Build-Clang.cppm | ||
| Crafter.Build-External.cppm | ||
| Crafter.Build-Implementation.cppm | ||
| Crafter.Build-Interface.cppm | ||
| Crafter.Build-Lint.cppm | ||
| Crafter.Build-Platform.cppm | ||
| Crafter.Build-Progress.cppm | ||
| Crafter.Build-Script.cppm | ||
| Crafter.Build-Shader.cppm | ||
| Crafter.Build-Test.cppm | ||
| Crafter.Build-Toolchain.cppm | ||
| Crafter.Build.cppm | ||