makeover-build
Build-script support for the make-family design system.
Every consumer materialises the same generated files from a build.rs. This is
that code, once, so no consumer keeps its own copy.
// build.rs
That writes themes/ beside the manifest and geometry.css, timing.css,
layout.css and typography.css under frontend/css/. The third argument is
the selector an app sets when the user has chosen touch density, if it offers
that choice.
Consumers wanting different paths call themes, geometry_css, timing_css,
layout_css and typography_css directly.
Drift checks
The hand-written half of a frontend states some of the same facts the generated
files ask the crates for, so it can drift where a generated file cannot. The
checks in drift fail the build when it has:
use ;
in_frontend.run;
in_frontend
.generated
// Reviewed: the card's shadow is the app's.
.allow
.run;
Why these files are generated
Tauri's resource globs are read by its CLI against the crate directory, so they
cannot point into a registry checkout or OUT_DIR. Materialising into the crate
keeps the source crate authoritative without vendoring a second copy that
drifts. Every path written here is expected to be gitignored.
themes clears stale .toml files before writing, so a theme removed or
renamed upstream does not linger in the bundle from a previous build.
Licence
MIT.