| commit | eb8c66fa080d36a35096f88c954030c1229017b7 | [log] [tgz] |
|---|---|---|
| author | brandjon <brandjon@google.com> | Thu Feb 28 15:17:52 2019 -0800 |
| committer | Copybara-Service <copybara-worker@google.com> | Thu Feb 28 15:19:36 2019 -0800 |
| tree | 73c81d579551f70e34599afbc7e1d18aaaa4d293 | |
| parent | 8494cc76109c76b1211bfcd253014e072570393f [diff] |
Add incompatible flag to make PY2 outputs suffixed This adds --incompatible_py2_outputs_are_suffixed, which makes it so Python 2 targets get built under an output root with the "-py2" suffix, and Python 3 targets get built under a root with no additional suffix. This means that the `bazel-bin` symlink contains Python 3 targets instead of Python 2 targets. This goes hand-in-hand with --incompatible_py3_is_default, which controls whether targets get built in the Python 2 or Python 3 configuration by default. Enabling just one flag or the other will cause the majority of targets to get built under an output root other than the one pointed to by `bazel-bin`, which is not very convenient. In general users and scripts are not supposed to care what the exact output path of a target is, but in practice they do, hence why this is an incompatible change. Work toward #6647. See #7593 for migration info. RELNOTES[INC]: Added --incompatible_py2_outputs_are_suffixed, for switching the bazel-bin symlink to point to Python 3 outputs instead of Python 2 outputs. See [#7593](https://github.com/bazelbuild/bazel/issues/7593). PiperOrigin-RevId: 236207234
{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.