4 ms·
It already does that. On first run, Bazel spawns a background process, which does all the work. In particular, it caches all the state (e. g. file hashes, parse
by lightgreen 6y ago
It already does that. On first run, Bazel spawns a background process, which does all the work. In particular, it caches all the state (e. g. file hashes, parsed build files etc.)
- MaxBarraclough 6y agoThanks for the reply. How does its package-detection stack up against CMake? One of CMake's advantages is that there's a Find module for most well-known libraries.
- lightgreen 6y agoI don't know much about it, because I believe dependency on installed in system libraries lead to non-reproducible builds (each machine is configured differently). Quick googling shows there is a lot of external rules for pkg-config https://github.com/cherrry/bazel_pkg_config https://github.com/cherrry/bazel_pkg_config or rules for building third-parties with cmake https://github.com/bazelbuild/rules_foreign_cc https://github.com/bazelbuild/rules_foreign_cc for example.