First of all, thanks for the awesome tool.
It really feels like an improvement over build scripts for code generation.
I use cargo px to generate ICU data for display purposes with icu_datagen.
However, cargo px regenerates the data module every build, which means that dependent crates also get rebuilt on every run.
It would be nice if we could tell cargo px a set of "input files" and it only regenerates the crate when those files change.
For now, I work around that by running cargo px only to regenerate the crate and using cargo normally otherwise.
But long term, it would be nice to not have to keep the difference in mind.
First of all, thanks for the awesome tool.
It really feels like an improvement over build scripts for code generation.
I use
cargo pxto generate ICU data for display purposes withicu_datagen.However,
cargo pxregenerates the data module every build, which means that dependent crates also get rebuilt on every run.It would be nice if we could tell
cargo pxa set of "input files" and it only regenerates the crate when those files change.For now, I work around that by running
cargo pxonly to regenerate the crate and usingcargonormally otherwise.But long term, it would be nice to not have to keep the difference in mind.