In order to synchronize build information across different processes, we have a generated C file that contains a small amount of git metadata -- the git hash, and an indication of whether the status is clean. Is there a way to make this work? My first thought is to write a genrule that will always rebuild the generated file when it's needed, but I don't see a way to do that.
--
You received this message because you are subscribed to the Google Groups "bazel-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to bazel-discus...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/bazel-discuss/ee60d275-8433-455c-a469-07799c4b1eaf%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
To view this discussion on the web visit https://groups.google.com/d/msgid/bazel-discuss/CABsbf%3DH7w20twunVztC0n04x253FO9UN%3D5_X9QBO8stiA6ap4A%40mail.gmail.com.
In order to synchronize build information across different processes, we have a generated C file that contains a small amount of git metadata -- the git hash, and an indication of whether the status is clean. Is there a way to make this work? My first thought is to write a genrule that will always rebuild the generated file when it's needed, but I don't see a way to do that.
--
You received this message because you are subscribed to the Google Groups "bazel-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to bazel-discus...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/bazel-discuss/ee60d275-8433-455c-a469-07799c4b1eaf%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.