commit | a091d90cded797ce8f6206b56ffd6f89e27e2c76 | [log] [tgz] |
---|---|---|
author | Googler <ilist@google.com> | Fri Apr 19 07:30:33 2024 -0700 |
committer | Copybara-Service <copybara-worker@google.com> | Fri Apr 19 07:32:11 2024 -0700 |
tree | de9e27390ae0fd9007647040a105c77ae39f766b | |
parent | 55dfe56cc10cef528c36f058553f4d77e5d90d10 [diff] |
Optimize _virtual_includes when paths are only stripped In this case it's not neccessary to create _virtual_includes, just setting the correct include path is enough. This should alleviate Windows problems with too long paths. Related: https://github.com/bazelbuild/bazel/issues/18683 PiperOrigin-RevId: 626360114 Change-Id: I4e7d8ee39e58dd27601f18c4a624c1d206785abe
{Fast, Correct} - Choose two
Build and test software of any size, quickly and reliably.
Speed up your builds and tests: Bazel rebuilds only what is necessary. With advanced local and distributed caching, optimized dependency analysis and parallel execution, you get fast and incremental builds.
One tool, multiple languages: Build and test Java, C++, Android, iOS, Go, and a wide variety of other language platforms. Bazel runs on Windows, macOS, and Linux.
Scalable: Bazel helps you scale your organization, codebase, and continuous integration solution. It handles codebases of any size, in multiple repositories or a huge monorepo.
Extensible to your needs: Easily add support for new languages and platforms with Bazel's familiar extension language. Share and re-use language rules written by the growing Bazel community.
Follow our tutorials:
To report a security issue, please email security@bazel.build with a description of the issue, the steps you took to create the issue, affected versions, and, if known, mitigations for the issue. Our vulnerability management team will respond within 3 working days of your email. If the issue is confirmed as a vulnerability, we will open a Security Advisory. This project follows a 90 day disclosure timeline.
See CONTRIBUTING.md