Guiguiprim

This awkward moment when the benchmark decided not to go your way. With the attached minimal project: Before this commit ```bash > cargo b --release > stat target/release/minimal-tonic-monomorphization -c "%s"...

For the time being a working work-around is to empty define `OBFSTR_SEED`.

Related to https://github.com/paritytech/cachepot/issues/137 Once built with a value for the environment variable, changing the environment variable does trigger a rebuild, but the `*.d` is not updated (probably false cache reuse)...

I discovered this issue with the following use case: including the current commit-id in a `--version` output. But it could impact other things. I was wondering if including the `build.rs`...

> I will look into it maybe the best way is just to launch the built `build.rs` from inside `cachepot` and parse the output. If that helps, the output of...

> Does your build script create any files or update any file's content? I do not create any file. But as previously stated, cargo does save its output into a...

> If the path is predictable, I simplified a bit, its more like `target/x86_64-pc-windows-msvc/release/build/my_lib-c89d522335dccf66/output`. I guess that `-c89d522335dccf66` can be deduced somehow.

`extern_path` only makes it possible for imported files to be generated in an other crate. Here I want the content of one proto file to be split in two crates....

Hi, I'm fine thank you. I need to see if I can manage to dedicate some time to it. In any case, what do you see by "in configuration" ?...

Again I might be able to get the v1 of this feature a go.