Brian Silverman

Redundant builds of dependencies due to shared objects in runfiles

3

I've noticed that all (transitive) dependencies of `rules_foreign_cc` rules tend to get compiled twice, due to [this code](https://github.com/bazelbuild/rules_foreign_cc/blob/86936d7b5b6022eba654fee1b0937915159e94ba/foreign_cc/private/framework.bzl#L517) in `cc_external_rule_impl` adding the dynamic libraries to the runfiles. I find this...

Transitive `cc_shared_library` doesn't work with inline functions

3

### Description of the bug: `cc_shared_library` and `dynamic_deps` deliberately link the shared libraries for only direct dependencies, while excluding the corresponding static libraries transitively. If any of the direct dependencies...

`cc_shared_library` dependency of `cc_test` results in redundant shared objects in runfiles

4

### Description of the bug: When a `cc_test` depends on a `cc_shared_library`, it correctly links against the `cc_shared_library`. However, the `cc_library` shared object still ends up in runfiles. This results...

Add support for exposing C/C++ dependencies

3

Some Python libraries (`numpy` is the most common example) support C/C++ code depending on them directly. To build this C/C++ code with Bazel, we need to expose the header files....

Use an absolute path to C/C++ compilers for better compatibility

3

[`toolchains_llvm`][1] only triggers its logic to locate files relative to the compiler wrapper when called with an absolute path, for example. Otherwise it assumes it's being called from the bazel...