3 ms·
That's specific to c. Bazel is often used in cases where you have multiple languages in use, and possibly dependencies between projects using different language
by thayne 4y ago
That's specific to c. Bazel is often used in cases where you have multiple languages in use, and possibly dependencies between projects using different languages.
> I just `find . -name "*.h"`
That sounds like it would cause problems with not triggering a build if a .h file is deleted. And would trigger unnecessary builds if any .h file is modified. But if your builds are that fast, maybe that isn't a problem.
- thechao 4y agoIt is specific to C/C++, for sure -- I started with that. ccache is going to be as fast as any checksum dependency tracker --- otherwise you're relying on a timestamp, which isn't any better than "bare" Make. We use `*.d` rules from the `-MD` flag to prevent the "deleted header" case. Considering the brevity of the Makefile (it looks like a "basic" build), performance, and the practical robustness, it's in a pretty great trade-off space.
- thayne 4y agoFrom what you've described I definitely don't think it would be worth migrating what you have to bazel. My point is just that there are environments where it does provide benefits.