-
Notifications
You must be signed in to change notification settings - Fork 108
/
workspace_setup_transitive_transitive.bzl
41 lines (31 loc) · 2.4 KB
/
workspace_setup_transitive_transitive.bzl
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
# Do not change the filename; it is part of the user interface.
def hedron_compile_commands_setup_transitive_transitive(module_ctx = None):
"""Part 3 of setting up a WORKSPACE to have hedron_compile_commands used within it.
module_ctx is for automatic-implicit use by bzlmod only.
Sorry it can't be unified with hedron_compile_commands_setup(). Bazel implementation restrictions.
"""
# Below the interface boundary:
# This is needed to get transitive dependencies of transitive dependencies--by calling their deps functions.
# Why?
# Bazel doesn't let you call a load except at the top level after v3 or so :/, so you have to resort to calling waves of workspace functions, one per each additional layer of transitive dependencies.
# For more info see:
# https://bazel.build/external/overview#shortcomings_of_the_workspace_system
# https://github.com/bazelbuild/bazel/issues/1550
# https://github.com/bazelbuild/bazel/issues/5815
# https://github.com/hedronvision/bazel-make-cc-https-easy/issues/14
# Unified setup for users' WORKSPACES and this workspace when used standalone.
# See invocations in:
# README.md (for WORKSPACE users)
# MODULE.bazel (for bzlmod users and for working on this repo standalone)
# If adding dependencies available via bzlmod, consider adding them to MODULE.bazel, too, and only loading them the WORKSPACE way when needed. For example:
# if not module_ctx:
# # Load bzlmod-available packages.
# Currently nothing to do -> no-op.
# So why is this even here? Enables future expansion (e.g to add transitive dependencies) without changing the user interface.
# Originally added for rules_python, which we reverted, but are keeping this interface to be used once it's fixed. See https://github.com/hedronvision/bazel-compile-commands-extractor/issues/168 for details.
pass
hedron_compile_commands_extension = module_extension( # Note: Doesn't break loading from WORKSPACE as far back as Bazel 5.0.0
implementation = hedron_compile_commands_setup_transitive_transitive,
# This extension is automatically loaded when using bzlmod (from MODULE.bazel) and will run the same function as WORKSPACE,
# but passes in a module_ctx object for advanced context of the whole project, allowing for complex, project wide modifiying extensions and distinguishing between WORKSPACE and bzlmod setups.
)