| commit | abfce25f38db0415c344d80cc4ca4ff92eb0feeb | [log] [tgz] |
|---|---|---|
| author | tomlu <tomlu@google.com> | Wed May 27 08:57:09 2020 -0700 |
| committer | Copybara-Service <copybara-worker@google.com> | Wed May 27 08:58:32 2020 -0700 |
| tree | 6a662421ff0f864b390af6ef8303ad5437d373b8 | |
| parent | 6c5f9115a48d11ef361f943469b4f8534e5e53ca [diff] |
Do not force users to specify '.so' or '.dll' manually for linkshared=1. This is legacy behaviour back when it was hard to do. These days, the toolchain can figure out an appropriate name for binaries and shared libraries, but only the binary code path was updated. TESTED=Added one tiny test to make sure it is no longer an error to create such a cc_binary. I don't know if it's safe to assert on exact name, seeing as the tests would then be platform specific. RELNOTES: linkshared=1 in cc_binary no longer requires '.so' or '.dll' in the target name PiperOrigin-RevId: 313398118
{Fast, Correct} - Choose two
Build and test software of any size, quickly and reliably.
Speed up your builds and tests: Bazel rebuilds only 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
