cc_shared_library: Don't fail when same shared lib is depended multiple times When using `--experimental-cc-shared-library`, the duplicate symbol check fails if a shared lib is linked multiple times. For example: ``` cc_library(name="X_static") cc_shared_library(name="X_shared", roots=[":X_static"]) cc_shared_library(name="A", dynamic_deps=[":X_shared"]) cc_shared_library(name="B", dynamic_deps=[":X_shared"]) cc_binary(name="test", dynamic_deps=[":A", ":B"]) ``` Will yield an error like: > in dynamic_deps attribute of cc_binary rule //:test: Two shared libraries in dependencies link the same library statically. Both //:X_shared and //:X_shared link statically //:X_static This fix checks to ensure it is truly different shared libraries exporting the same static lib. Closes #12981. PiperOrigin-RevId: 356482606
{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