[bazel-discuss] How can I introduce the dependency of another external library in the build file of an external library?

[shuman zhuang]

Description: When using Bazel to build the Velox project, I encountered a compilation issue related to the Folly dependency. I've set up Folly using a path override locally and can compile it successfully by itself, but I am unable to compile within the Velox root directory using Bazel.

Steps to Reproduce:

1.Use local path override for Folly:

local_path_override(

    module_name = "folly_module",

    path = "/path/to/local/folly",

)

2.Run Bazel build in the Velox root directory:

bazel build //velox/common/encode:velox_encode

Error messages:

1.Dependencies defined in WORKSPACE are not visible.

In Velox dir:

2.Dependencies defined in MODULE.bzl are visible.

All module could load successfully

3.Bazel compiles successfully when run directly in the Folly directory with same MODULE.bazel and WORKSPACE files list above

Environment:

Operating System: CentOS 7

GCC Version: 12

Bazel Version: 7.4.1

Expected Behavior: I expect to successfully build targets within the Velox project that include my locally modified version of Folly, using the path override method.

Actual Behavior: Errors were reported indicating that dependencies are not visible, although compiling directly within the Folly directory succeeds.

Suggestions or Clues: I am looking for guidance on how to improve dependency visibility in this setup.