| commit | 9b31fbd261e3ee558746a8348d0cf7eb2a1edee2 | [log] [tgz] |
|---|---|---|
| author | Klaus Aehlig <aehlig@google.com> | Thu Feb 07 03:27:57 2019 -0800 |
| committer | Copybara-Service <copybara-piper@google.com> | Thu Feb 07 03:29:50 2019 -0800 |
| tree | 426cf62f17d27d2ee5557860fdb952af0ba748fb | |
| parent | ce10ff60d96d0bb56138190087ef3a3a56c5bbf3 [diff] |
Allow the import of private symols from a resolved file A repository resolved file contains a trace of the actual repository rules called from a WORKSPACE file. This is the case, even if a repository rule is not called directly but via macro. Now, macros may refer to symbols private to the file they are defined in. Therefore, a resolved file may legitimately contain a reference to a private symbol. However, when using a resolved file, this import is currently disallowed. Fix this. Fixes #6835. Change-Id: Id890388c2c480fcb958e0468bf8da6c02dd46c2a PiperOrigin-RevId: 232842034
{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.