commit | 210428cafd40c9c25787906cb2422085b70b8f30 | [log] [tgz] |
---|---|---|
author | pcloudy <pcloudy@google.com> | Tue Jun 25 02:47:02 2019 -0700 |
committer | Copybara-Service <copybara-worker@google.com> | Tue Jun 25 02:48:07 2019 -0700 |
tree | bc6c0a5e7adc3622116f8df8359aa88f9497330b | |
parent | d4589630428c1c1bc08a9baf36257e636fe9d746 [diff] |
Remove runtime dynamic libraries from default output group of cc_binary Bazel copies dynamic libraries to the binary's directory so that it's available at runtime. Before this change, all runtime dynamic libraries are added into the default output group, this is bad because it makes the target name (eg. //:foo.dll) refer to multiple artifacts. In this change, we are having a separate output group (runtime_dynamic_libraries) for them. Fixes https://github.com/bazelbuild/bazel/issues/8707 RELNOTES: The runtime dynamic libraries are no longer in default output group of cc_binary. PiperOrigin-RevId: 254931976
{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.