| commit | f2b386cedb3ec262c05139ffdc38eda7f57a7488 | [log] [tgz] |
|---|---|---|
| author | twigg <twigg@google.com> | Tue Apr 30 16:47:52 2019 -0700 |
| committer | Copybara-Service <copybara-worker@google.com> | Tue Apr 30 16:49:07 2019 -0700 |
| tree | b8854a65cbcdefaa2438bc1190149ffe06dcac33 | |
| parent | 849666594ab5f9acfd803101c0708504aa8784ab [diff] |
Rewrite visibility advice in build style guide. Directly from the prior conversation, say both __pkg__ and __subpackages__ are equally appropriate and acceptable. Should I add a section saying to consider __subpackages__ to avoid churn when clients refactor their code? Re-order so the first thing said is the 'thesis' that "Visibility should be scoped as tightly as possible" (since that seems to be the main takeaway for the section). From my own experience, directly caution against using package default_visibility. Note, I am convinced there is a bug regarding default_visibility that is causing too many files to be exposed. Files used as inputs are implicitly exported with default_visibility even if exports_files is never used. This bug as well as people overusing default_visibility has caused substantial headaches when trying to refactor code. RELNOTES: Update visibility advice in build-style PiperOrigin-RevId: 246048587
{Fast, Correct} - Choose two
Build and test software of any size, quickly and reliably.
Speed up your builds and tests: Bazel only rebuilds 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:
See CONTRIBUTING.md
Bazel is released in ‘Beta’. See the product roadmap to learn about the path toward a stable 1.0 release.