commit | a1068c44a700ec2cff84cbd12592e9bfea25d754 | [log] [tgz] |
---|---|---|
author | Jingwen Chen <jingwen@google.com> | Wed Mar 21 06:50:24 2018 -0700 |
committer | Copybara-Service <copybara-piper@google.com> | Wed Mar 21 06:52:22 2018 -0700 |
tree | 73a742876ccc522f0de74d04b3701aea060d6d5a | |
parent | 1762772f482e6bdeb937b830dca9ba71f8f5edf7 [diff] |
NDK cc_toolchains: include bundled runtime libraries in cc_toolchain.all_files Currently, generated NDK `cc_toolchain.all_files` filegroups do not glob the STL's static and dynamic runtime libraries, which includes important files like `libandroid_support.a` and `libc++.{so, a}`. This introduces sandboxed link time errors as @steeve discovered at https://github.com/bazelbuild/bazel/issues/3923#issuecomment-372750002 This PR adds the two filegroups to the respective toolchain's `all-files` filegroup to make them part of the toolchain's output in the sandbox. This generates a BUILD.bazel file like this: https://gist.github.com/jin/7d9fcf924fa33ab8fbc4c43c97676ab3 Fixes https://github.com/bazelbuild/bazel/issues/4864 Closes #4866. PiperOrigin-RevId: 189900428
{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.