--
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-discuss+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/bazel-discuss/e257d5be-f014-4548-8b11-355d7f653c78%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
We do not have that.
Why do you need to do `bazel clean` at all? Our aim is to make sure you never need to do bazel clean, so if you do, something is wrong.
On Mon, Aug 28, 2017 at 11:43 PM, Break Yang <bre...@gmail.com> wrote:
Hi all,We currently have a huge third party dependencies called `pcl`, which takes more than 10 minutes to build. We expect it to be built once and be there for good. The problem is that when `bazel clean` is called, `pcl` (or its build status) gets cleaned as well so the next time we build something depending on it, we need to wait another 10+ minute.In general, since external dependencies do not change (or do not change that often), is there a way to do `bazel clean` without touching them, to save some unnecessary rebuild?Thanks a lot!Best,-Break
--
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/e257d5be-f014-4548-8b11-355d7f653c78%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.