|
|
|
|
|
by SolarNet
2417 days ago
|
|
I feel like that's a misunderstanding of the issue. Recursive dependencies are orthogonal to the issue of having an ecosystem of dependencies. There is a pattern for recursive dependency management (did you notice the `boost_deps` recursive dependency call?) that is currently fine for production that recursive workspaces will make better. Also as demonstrated Boost is way easier to include in bazel than make which was the original issue under discussion. I make a library that depends on boost, here is how you use it: git_repository(
name="foo"
...
)
load("@foo//:foo/foo.bzl", "foo_deps")
foo_deps()
magic |
|