diff --git a/concepts/build-files.mdx b/concepts/build-files.mdx index b85f472c..ec87f4db 100644 --- a/concepts/build-files.mdx +++ b/concepts/build-files.mdx @@ -132,6 +132,23 @@ for anyone to create new rules. and binaries and tests can depend on libraries, with the expected separate-compilation behavior. + + + + + +
+ + Labels + + + + Dependencies + +
+ ## File encoding `BUILD` and `.bzl` files should be encoded in UTF-8, of which ASCII is a valid diff --git a/concepts/build-ref.mdx b/concepts/build-ref.mdx index 67c5f1bd..0af78970 100644 --- a/concepts/build-ref.mdx +++ b/concepts/build-ref.mdx @@ -99,3 +99,7 @@ package groups they include. The only allowed ways to refer to them are from the the `package` function; they do not generate or consume files. For more information, refer to the [`package_group` documentation](/reference/be/functions#package_group). + + + Labels + diff --git a/concepts/dependencies.mdx b/concepts/dependencies.mdx index e03c1af7..39fef86e 100644 --- a/concepts/dependencies.mdx +++ b/concepts/dependencies.mdx @@ -366,3 +366,21 @@ filegroup( ``` You can then reference the label `my_data` as the data dependency in your test. + + + + + + +
+ + BUILD files + + + + Visibility + +
+ diff --git a/concepts/labels.mdx b/concepts/labels.mdx index aec9adcf..5b0b1c6a 100644 --- a/concepts/labels.mdx +++ b/concepts/labels.mdx @@ -241,3 +241,20 @@ the build. This directed acyclic graph over targets is called the _target graph_ or _build dependency graph_, and is the domain over which the [Bazel Query tool](/query/guide) operates. + + + + + + +
+ + Targets + + + + BUILD files + +
diff --git a/reference/command-line-reference.mdx b/reference/command-line-reference.mdx index b20c0bd9..6573c55f 100644 --- a/reference/command-line-reference.mdx +++ b/reference/command-line-reference.mdx @@ -1900,12 +1900,6 @@ Options relating to query output and semantics: Tags: [`terminal_output`](#effect_tag_TERMINAL_OUTPUT) -`--[no]incompatible_package_group_build_output` default: "false" -: If enabled, `blaze query --output=build` will output `package_group` targets. - - Tags: - [`terminal_output`](#effect_tag_TERMINAL_OUTPUT), [`incompatible_change`](#metadata_tag_INCOMPATIBLE_CHANGE) - `--[no]incompatible_package_group_includes_double_slash` default: "true" : If enabled, when outputting package_group's `packages` attribute, the leading `//` will not be omitted. @@ -3081,6 +3075,12 @@ Options that affect how strictly Bazel enforces valid build inputs (rule definit Tags: [`build_file_semantics`](#effect_tag_BUILD_FILE_SEMANTICS) +`--[no]experimental_check_desugar_deps` default: "true" +: Whether to double-check correct desugaring at Android binary level. + + Tags: + [`eagerness_to_exit`](#effect_tag_EAGERNESS_TO_EXIT), [`loading_and_analysis`](#effect_tag_LOADING_AND_ANALYSIS), [`experimental`](#metadata_tag_EXPERIMENTAL) + `--[no]experimental_enforce_transitive_visibility` default: "false" : If true, enable package()s to set the transitive_visibility attribute to restrict which packages may depend on them. @@ -3284,6 +3284,12 @@ Options that trigger optimizations of the build time: Tags: [`loading_and_analysis`](#effect_tag_LOADING_AND_ANALYSIS), [`execution`](#effect_tag_EXECUTION), [`changes_inputs`](#effect_tag_CHANGES_INPUTS), [`experimental`](#metadata_tag_EXPERIMENTAL) +`--[no]incremental_dexing` default: "true" +: Does most of the work for dexing separately for each Jar file. + + Tags: + [`affects_outputs`](#effect_tag_AFFECTS_OUTPUTS), [`loading_and_analysis`](#effect_tag_LOADING_AND_ANALYSIS), [`loses_incremental_state`](#effect_tag_LOSES_INCREMENTAL_STATE) + `--[no]objc_use_dotd_pruning` default: "true" : If set, .d files emitted by clang will be used to prune the set of inputs passed into objc compiles. @@ -3366,9 +3372,6 @@ Miscellaneous options, not otherwise categorized.: Tags: [`affects_outputs`](#effect_tag_AFFECTS_OUTPUTS), [`experimental`](#metadata_tag_EXPERIMENTAL) -`--experimental_turbine_cpu_reservation=<an integer>` default: "1" -: The number of CPUs to reserve for Turbine. - `--[no]explicit_java_test_deps` default: "false" : Explicitly specify a dependency to JUnit or Hamcrest in a java_test instead of accidentally obtaining from the TestRunner's deps. Only works for bazel right now. @@ -5750,6 +5753,12 @@ Options that affect how strictly Bazel enforces valid build inputs (rule definit Tags: [`build_file_semantics`](#effect_tag_BUILD_FILE_SEMANTICS) +`--[no]experimental_check_desugar_deps` default: "true" +: Whether to double-check correct desugaring at Android binary level. + + Tags: + [`eagerness_to_exit`](#effect_tag_EAGERNESS_TO_EXIT), [`loading_and_analysis`](#effect_tag_LOADING_AND_ANALYSIS), [`experimental`](#metadata_tag_EXPERIMENTAL) + `--[no]experimental_enforce_transitive_visibility` default: "false" : If true, enable package()s to set the transitive_visibility attribute to restrict which packages may depend on them. @@ -5953,6 +5962,12 @@ Options that trigger optimizations of the build time: Tags: [`loading_and_analysis`](#effect_tag_LOADING_AND_ANALYSIS), [`execution`](#effect_tag_EXECUTION), [`changes_inputs`](#effect_tag_CHANGES_INPUTS), [`experimental`](#metadata_tag_EXPERIMENTAL) +`--[no]incremental_dexing` default: "true" +: Does most of the work for dexing separately for each Jar file. + + Tags: + [`affects_outputs`](#effect_tag_AFFECTS_OUTPUTS), [`loading_and_analysis`](#effect_tag_LOADING_AND_ANALYSIS), [`loses_incremental_state`](#effect_tag_LOSES_INCREMENTAL_STATE) + `--[no]objc_use_dotd_pruning` default: "true" : If set, .d files emitted by clang will be used to prune the set of inputs passed into objc compiles. @@ -6035,9 +6050,6 @@ Miscellaneous options, not otherwise categorized.: Tags: [`affects_outputs`](#effect_tag_AFFECTS_OUTPUTS), [`experimental`](#metadata_tag_EXPERIMENTAL) -`--experimental_turbine_cpu_reservation=<an integer>` default: "1" -: The number of CPUs to reserve for Turbine. - `--[no]explicit_java_test_deps` default: "false" : Explicitly specify a dependency to JUnit or Hamcrest in a java_test instead of accidentally obtaining from the TestRunner's deps. Only works for bazel right now. @@ -6359,12 +6371,6 @@ Options relating to query output and semantics: Tags: [`terminal_output`](#effect_tag_TERMINAL_OUTPUT) -`--[no]incompatible_package_group_build_output` default: "false" -: If enabled, `blaze query --output=build` will output `package_group` targets. - - Tags: - [`terminal_output`](#effect_tag_TERMINAL_OUTPUT), [`incompatible_change`](#metadata_tag_INCOMPATIBLE_CHANGE) - `--[no]incompatible_package_group_includes_double_slash` default: "true" : If enabled, when outputting package_group's `packages` attribute, the leading `//` will not be omitted. @@ -7564,6 +7570,12 @@ Options that affect how strictly Bazel enforces valid build inputs (rule definit Tags: [`build_file_semantics`](#effect_tag_BUILD_FILE_SEMANTICS) +`--[no]experimental_check_desugar_deps` default: "true" +: Whether to double-check correct desugaring at Android binary level. + + Tags: + [`eagerness_to_exit`](#effect_tag_EAGERNESS_TO_EXIT), [`loading_and_analysis`](#effect_tag_LOADING_AND_ANALYSIS), [`experimental`](#metadata_tag_EXPERIMENTAL) + `--[no]experimental_enforce_transitive_visibility` default: "false" : If true, enable package()s to set the transitive_visibility attribute to restrict which packages may depend on them. @@ -7767,6 +7779,12 @@ Options that trigger optimizations of the build time: Tags: [`loading_and_analysis`](#effect_tag_LOADING_AND_ANALYSIS), [`execution`](#effect_tag_EXECUTION), [`changes_inputs`](#effect_tag_CHANGES_INPUTS), [`experimental`](#metadata_tag_EXPERIMENTAL) +`--[no]incremental_dexing` default: "true" +: Does most of the work for dexing separately for each Jar file. + + Tags: + [`affects_outputs`](#effect_tag_AFFECTS_OUTPUTS), [`loading_and_analysis`](#effect_tag_LOADING_AND_ANALYSIS), [`loses_incremental_state`](#effect_tag_LOSES_INCREMENTAL_STATE) + `--[no]objc_use_dotd_pruning` default: "true" : If set, .d files emitted by clang will be used to prune the set of inputs passed into objc compiles. @@ -7849,9 +7867,6 @@ Miscellaneous options, not otherwise categorized.: Tags: [`affects_outputs`](#effect_tag_AFFECTS_OUTPUTS), [`experimental`](#metadata_tag_EXPERIMENTAL) -`--experimental_turbine_cpu_reservation=<an integer>` default: "1" -: The number of CPUs to reserve for Turbine. - `--[no]explicit_java_test_deps` default: "false" : Explicitly specify a dependency to JUnit or Hamcrest in a java_test instead of accidentally obtaining from the TestRunner's deps. Only works for bazel right now. @@ -9199,6 +9214,12 @@ Options that affect how strictly Bazel enforces valid build inputs (rule definit Tags: [`build_file_semantics`](#effect_tag_BUILD_FILE_SEMANTICS) +`--[no]experimental_check_desugar_deps` default: "true" +: Whether to double-check correct desugaring at Android binary level. + + Tags: + [`eagerness_to_exit`](#effect_tag_EAGERNESS_TO_EXIT), [`loading_and_analysis`](#effect_tag_LOADING_AND_ANALYSIS), [`experimental`](#metadata_tag_EXPERIMENTAL) + `--[no]experimental_enforce_transitive_visibility` default: "false" : If true, enable package()s to set the transitive_visibility attribute to restrict which packages may depend on them. @@ -9402,6 +9423,12 @@ Options that trigger optimizations of the build time: Tags: [`loading_and_analysis`](#effect_tag_LOADING_AND_ANALYSIS), [`execution`](#effect_tag_EXECUTION), [`changes_inputs`](#effect_tag_CHANGES_INPUTS), [`experimental`](#metadata_tag_EXPERIMENTAL) +`--[no]incremental_dexing` default: "true" +: Does most of the work for dexing separately for each Jar file. + + Tags: + [`affects_outputs`](#effect_tag_AFFECTS_OUTPUTS), [`loading_and_analysis`](#effect_tag_LOADING_AND_ANALYSIS), [`loses_incremental_state`](#effect_tag_LOSES_INCREMENTAL_STATE) + `--[no]objc_use_dotd_pruning` default: "true" : If set, .d files emitted by clang will be used to prune the set of inputs passed into objc compiles. @@ -9484,9 +9511,6 @@ Miscellaneous options, not otherwise categorized.: Tags: [`affects_outputs`](#effect_tag_AFFECTS_OUTPUTS), [`experimental`](#metadata_tag_EXPERIMENTAL) -`--experimental_turbine_cpu_reservation=<an integer>` default: "1" -: The number of CPUs to reserve for Turbine. - `--[no]explicit_java_test_deps` default: "false" : Explicitly specify a dependency to JUnit or Hamcrest in a java_test instead of accidentally obtaining from the TestRunner's deps. Only works for bazel right now. @@ -10789,12 +10813,6 @@ Options relating to query output and semantics: Tags: [`terminal_output`](#effect_tag_TERMINAL_OUTPUT) -`--[no]incompatible_package_group_build_output` default: "false" -: If enabled, `blaze query --output=build` will output `package_group` targets. - - Tags: - [`terminal_output`](#effect_tag_TERMINAL_OUTPUT), [`incompatible_change`](#metadata_tag_INCOMPATIBLE_CHANGE) - `--[no]incompatible_package_group_includes_double_slash` default: "true" : If enabled, when outputting package_group's `packages` attribute, the leading `//` will not be omitted. @@ -12192,6 +12210,12 @@ Options that affect how strictly Bazel enforces valid build inputs (rule definit Tags: [`build_file_semantics`](#effect_tag_BUILD_FILE_SEMANTICS) +`--[no]experimental_check_desugar_deps` default: "true" +: Whether to double-check correct desugaring at Android binary level. + + Tags: + [`eagerness_to_exit`](#effect_tag_EAGERNESS_TO_EXIT), [`loading_and_analysis`](#effect_tag_LOADING_AND_ANALYSIS), [`experimental`](#metadata_tag_EXPERIMENTAL) + `--[no]experimental_enforce_transitive_visibility` default: "false" : If true, enable package()s to set the transitive_visibility attribute to restrict which packages may depend on them. @@ -12395,6 +12419,12 @@ Options that trigger optimizations of the build time: Tags: [`loading_and_analysis`](#effect_tag_LOADING_AND_ANALYSIS), [`execution`](#effect_tag_EXECUTION), [`changes_inputs`](#effect_tag_CHANGES_INPUTS), [`experimental`](#metadata_tag_EXPERIMENTAL) +`--[no]incremental_dexing` default: "true" +: Does most of the work for dexing separately for each Jar file. + + Tags: + [`affects_outputs`](#effect_tag_AFFECTS_OUTPUTS), [`loading_and_analysis`](#effect_tag_LOADING_AND_ANALYSIS), [`loses_incremental_state`](#effect_tag_LOSES_INCREMENTAL_STATE) + `--[no]objc_use_dotd_pruning` default: "true" : If set, .d files emitted by clang will be used to prune the set of inputs passed into objc compiles. @@ -12477,9 +12507,6 @@ Miscellaneous options, not otherwise categorized.: Tags: [`affects_outputs`](#effect_tag_AFFECTS_OUTPUTS), [`experimental`](#metadata_tag_EXPERIMENTAL) -`--experimental_turbine_cpu_reservation=<an integer>` default: "1" -: The number of CPUs to reserve for Turbine. - `--[no]explicit_java_test_deps` default: "false" : Explicitly specify a dependency to JUnit or Hamcrest in a java_test instead of accidentally obtaining from the TestRunner's deps. Only works for bazel right now. diff --git a/rules/lib/builtins/actions.mdx b/rules/lib/builtins/actions.mdx index 0758c56d..34ace9c8 100644 --- a/rules/lib/builtins/actions.mdx +++ b/rules/lib/builtins/actions.mdx @@ -137,7 +137,7 @@ Creates multiple actions based on the files within one or more input directories ## run ``` -None actions.run(*, outputs, inputs=[], unused_inputs_list=None, executable, tools=unbound, arguments=[], mnemonic=None, progress_message=None, use_default_shell_env=False, env=None, execution_requirements=None, input_manifests=None, exec_group=None, shadowed_action=None, resource_set=None, toolchain=unbound) +None actions.run(*, outputs, inputs=[], unused_inputs_list=None, executable, tools=unbound, arguments=[], mnemonic=None, progress_message=None, use_default_shell_env=False, env=None, execution_requirements=None, input_manifests=None, exec_group=None, shadowed_action=None, resource_set=None, toolchain=unbound, timeout=None) ``` Creates an action that runs an executable. [See example of use](https://github.com/bazelbuild/examples/tree/main/rules/actions_run/execute.bzl). @@ -162,11 +162,12 @@ Creates an action that runs an executable. [See example of use](https://github.c | `shadowed_action` | [Action](../builtins/Action); default is `None` Runs the action using the given shadowed action's inputs and environment added to the action's inputs list and environment. The action environment can overwrite any of the shadowed action's environment variables. If none, uses only the action's inputs and given environment. | | `resource_set` | callable; or `None`; default is `None` A callback function that returns a resource set dictionary, used to estimate resource usage at execution time if this action is run locally. The function accepts two positional arguments: a string representing an OS name (e.g. "osx"), and an integer representing the number of inputs to the action. The returned dictionary may contain the following entries, each of which may be a float or an int: * "cpu": number of CPUs; default 1* "memory": in MB; default 250* "local_test": number of local tests; default 1 If this parameter is set to `None` , the default values are used. The callback must be top-level (lambda and nested functions aren't allowed). | | `toolchain` | [Label](../builtins/Label); or [string](../core/string); or `None`; default is `unbound` Toolchain type of the executable or tools used in this action. If executable and tools are not coming from a toolchain, set this parameter to `None`. If executable and tools are coming from a toolchain, toolchain type must be set so that the action executes on the correct execution platform. Note that the rule which creates this action needs to define this toolchain inside its 'rule()' function. When `toolchain` and `exec_group` parameters are both set, `exec_group` will be used. An error is raised in case the `exec_group` doesn't specify the same toolchain. | +| `timeout` | [int](../core/int); or `None`; default is `None` Maximum duration of the action in seconds, or `None` for no timeout. If the action runs longer than this, it is killed and the build fails. Overrides any rule-level `timeout` attribute for this specific action. Must be a non-negative integer; 0 is treated the same as `None`. | ## run_shell ``` -None actions.run_shell(*, outputs, inputs=[], tools=unbound, arguments=[], mnemonic=None, command, progress_message=None, use_default_shell_env=False, env=None, execution_requirements=None, input_manifests=None, exec_group=None, shadowed_action=None, resource_set=None, toolchain=unbound) +None actions.run_shell(*, outputs, inputs=[], tools=unbound, arguments=[], mnemonic=None, command, progress_message=None, use_default_shell_env=False, env=None, execution_requirements=None, input_manifests=None, exec_group=None, shadowed_action=None, resource_set=None, toolchain=unbound, timeout=None) ``` Creates an action that runs a shell command. [See example of use](https://github.com/bazelbuild/examples/tree/main/rules/shell_command/rules.bzl). @@ -190,6 +191,7 @@ Creates an action that runs a shell command. [See example of use](https://github | `shadowed_action` | [Action](../builtins/Action); default is `None` Runs the action using the given shadowed action's discovered inputs added to the action's inputs list. If none, uses only the action's inputs. | | `resource_set` | callable; or `None`; default is `None` A callback function for estimating resource usage if run locally. See[`ctx.actions.run()`](#run.resource_set). | | `toolchain` | [Label](../builtins/Label); or [string](../core/string); or `None`; default is `unbound` Toolchain type of the executable or tools used in this action. If executable and tools are not coming from a toolchain, set this parameter to `None`. If executable and tools are coming from a toolchain, toolchain type must be set so that the action executes on the correct execution platform. Note that the rule which creates this action needs to define this toolchain inside its 'rule()' function. When `toolchain` and `exec_group` parameters are both set, `exec_group` will be used. An error is raised in case the `exec_group` doesn't specify the same toolchain. | +| `timeout` | [int](../core/int); or `None`; default is `None` Maximum duration of the action in seconds, or `None` for no timeout. If the action runs longer than this, it is killed and the build fails. Overrides any rule-level `timeout` attribute for this specific action. Must be a non-negative integer; 0 is treated the same as `None`. | ## symlink diff --git a/upstream b/upstream index de0d9098..7943053f 160000 --- a/upstream +++ b/upstream @@ -1 +1 @@ -Subproject commit de0d9098f358e8a7db798f4faf471f54b0737dc3 +Subproject commit 7943053f89099db8feaec6e16c257c249cce5ca7 diff --git a/versions/6.5.0/concepts/build-files.mdx b/versions/6.5.0/concepts/build-files.mdx index b05e79e0..b468b9f9 100644 --- a/versions/6.5.0/concepts/build-files.mdx +++ b/versions/6.5.0/concepts/build-files.mdx @@ -125,3 +125,10 @@ for anyone to create new rules. programming language. Libraries can depend on other libraries, and binaries and tests can depend on libraries, with the expected separate-compilation behavior. + + + + + + +
LabelsDependencies
diff --git a/versions/6.5.0/concepts/build-ref.mdx b/versions/6.5.0/concepts/build-ref.mdx index 3cc6bf3a..b7f338ee 100644 --- a/versions/6.5.0/concepts/build-ref.mdx +++ b/versions/6.5.0/concepts/build-ref.mdx @@ -109,3 +109,7 @@ package groups they include. The only allowed ways to refer to them are from the the `package` function; they do not generate or consume files. For more information, refer to the [`package_group` documentation](/reference/be/functions#package_group). + + + Labels + diff --git a/versions/6.5.0/concepts/dependencies.mdx b/versions/6.5.0/concepts/dependencies.mdx index 345b6246..52f28620 100644 --- a/versions/6.5.0/concepts/dependencies.mdx +++ b/versions/6.5.0/concepts/dependencies.mdx @@ -344,3 +344,11 @@ filegroup( ``` You can then reference the label `my_data` as the data dependency in your test. + + + + + + +
BUILD filesVisibility
+ diff --git a/versions/6.5.0/concepts/labels.mdx b/versions/6.5.0/concepts/labels.mdx index c1506361..286804f7 100644 --- a/versions/6.5.0/concepts/labels.mdx +++ b/versions/6.5.0/concepts/labels.mdx @@ -212,3 +212,10 @@ the build. This directed acyclic graph over targets is called the _target graph_ or _build dependency graph_, and is the domain over which the [Bazel Query tool](/versions/6.5.0/docs/query-how-to) operates. + + + + + + +
TargetsBUILD files
diff --git a/versions/6.5.0/versions/index.mdx b/versions/6.5.0/versions/index.mdx index 09904b7e..f71981be 100644 --- a/versions/6.5.0/versions/index.mdx +++ b/versions/6.5.0/versions/index.mdx @@ -10,3 +10,7 @@ version support. For now, to see documentation for older Bazel versions, go to [docs.bazel.build](https://docs.bazel.build/). + + + To the Archives! + diff --git a/versions/7.6.1/concepts/build-files.mdx b/versions/7.6.1/concepts/build-files.mdx index 010e0491..4e4473fc 100644 --- a/versions/7.6.1/concepts/build-files.mdx +++ b/versions/7.6.1/concepts/build-files.mdx @@ -132,3 +132,10 @@ for anyone to create new rules. programming language. Libraries can depend on other libraries, and binaries and tests can depend on libraries, with the expected separate-compilation behavior. + + + + + + +
LabelsDependencies
diff --git a/versions/7.6.1/concepts/build-ref.mdx b/versions/7.6.1/concepts/build-ref.mdx index 177b315b..911028a7 100644 --- a/versions/7.6.1/concepts/build-ref.mdx +++ b/versions/7.6.1/concepts/build-ref.mdx @@ -97,3 +97,7 @@ package groups they include. The only allowed ways to refer to them are from the the `package` function; they do not generate or consume files. For more information, refer to the [`package_group` documentation](/versions/7.6.1/reference/be/functions#package_group). + + + Labels + \ No newline at end of file diff --git a/versions/7.6.1/concepts/dependencies.mdx b/versions/7.6.1/concepts/dependencies.mdx index 0b526039..0c92f1ea 100644 --- a/versions/7.6.1/concepts/dependencies.mdx +++ b/versions/7.6.1/concepts/dependencies.mdx @@ -347,3 +347,8 @@ filegroup( ``` You can then reference the label `my_data` as the data dependency in your test. + + + +
BUILD filesVisibility
+ diff --git a/versions/7.6.1/concepts/labels.mdx b/versions/7.6.1/concepts/labels.mdx index 8ed20174..60891bc7 100644 --- a/versions/7.6.1/concepts/labels.mdx +++ b/versions/7.6.1/concepts/labels.mdx @@ -228,3 +228,10 @@ the build. This directed acyclic graph over targets is called the _target graph_ or _build dependency graph_, and is the domain over which the [Bazel Query tool](/versions/7.6.1/query/guide) operates. + + + + + + +
TargetsBUILD files
diff --git a/versions/7.6.1/versions/index.mdx b/versions/7.6.1/versions/index.mdx index ad1492e5..c92a15b6 100644 --- a/versions/7.6.1/versions/index.mdx +++ b/versions/7.6.1/versions/index.mdx @@ -11,3 +11,7 @@ version support. For now, to see documentation for older Bazel versions, go to [docs.bazel.build](https://docs.bazel.build/). + + + To the Archives! + diff --git a/versions/7.7.1/concepts/build-files.mdx b/versions/7.7.1/concepts/build-files.mdx index 819f2374..bcd6ef60 100644 --- a/versions/7.7.1/concepts/build-files.mdx +++ b/versions/7.7.1/concepts/build-files.mdx @@ -132,3 +132,10 @@ for anyone to create new rules. programming language. Libraries can depend on other libraries, and binaries and tests can depend on libraries, with the expected separate-compilation behavior. + + + + + + +
LabelsDependencies
diff --git a/versions/7.7.1/concepts/build-ref.mdx b/versions/7.7.1/concepts/build-ref.mdx index c8d6b6d8..b2b952a6 100644 --- a/versions/7.7.1/concepts/build-ref.mdx +++ b/versions/7.7.1/concepts/build-ref.mdx @@ -97,3 +97,7 @@ package groups they include. The only allowed ways to refer to them are from the the `package` function; they do not generate or consume files. For more information, refer to the [`package_group` documentation](/versions/7.7.1/reference/be/functions#package_group). + + + Labels + \ No newline at end of file diff --git a/versions/7.7.1/concepts/dependencies.mdx b/versions/7.7.1/concepts/dependencies.mdx index 3358c7c1..0df26784 100644 --- a/versions/7.7.1/concepts/dependencies.mdx +++ b/versions/7.7.1/concepts/dependencies.mdx @@ -325,3 +325,11 @@ filegroup( ``` You can then reference the label `my_data` as the data dependency in your test. + + + + + + +
BUILD filesVisibility
+ diff --git a/versions/7.7.1/concepts/labels.mdx b/versions/7.7.1/concepts/labels.mdx index 9780c61c..520dfec2 100644 --- a/versions/7.7.1/concepts/labels.mdx +++ b/versions/7.7.1/concepts/labels.mdx @@ -228,3 +228,10 @@ the build. This directed acyclic graph over targets is called the _target graph_ or _build dependency graph_, and is the domain over which the [Bazel Query tool](/versions/7.7.1/query/guide) operates. + + + + + + +
TargetsBUILD files
diff --git a/versions/8.0.1/concepts/build-files.mdx b/versions/8.0.1/concepts/build-files.mdx index 7e730fd3..662aec5e 100644 --- a/versions/8.0.1/concepts/build-files.mdx +++ b/versions/8.0.1/concepts/build-files.mdx @@ -132,3 +132,12 @@ for anyone to create new rules. programming language. Libraries can depend on other libraries, and binaries and tests can depend on libraries, with the expected separate-compilation behavior. + + + + + + +
LabelsDependencies
diff --git a/versions/8.0.1/concepts/build-ref.mdx b/versions/8.0.1/concepts/build-ref.mdx index fdcaa2fe..130ec5e5 100644 --- a/versions/8.0.1/concepts/build-ref.mdx +++ b/versions/8.0.1/concepts/build-ref.mdx @@ -97,3 +97,7 @@ package groups they include. The only allowed ways to refer to them are from the the `package` function; they do not generate or consume files. For more information, refer to the [`package_group` documentation](/versions/8.0.1/reference/be/functions#package_group). + + + Labels + \ No newline at end of file diff --git a/versions/8.0.1/concepts/dependencies.mdx b/versions/8.0.1/concepts/dependencies.mdx index 5711e4fc..0bc129e6 100644 --- a/versions/8.0.1/concepts/dependencies.mdx +++ b/versions/8.0.1/concepts/dependencies.mdx @@ -296,3 +296,13 @@ filegroup( ``` You can then reference the label `my_data` as the data dependency in your test. + + + + + + +
BUILD filesVisibility
+ diff --git a/versions/8.0.1/concepts/labels.mdx b/versions/8.0.1/concepts/labels.mdx index d62146ab..f02c9395 100644 --- a/versions/8.0.1/concepts/labels.mdx +++ b/versions/8.0.1/concepts/labels.mdx @@ -239,3 +239,12 @@ the build. This directed acyclic graph over targets is called the _target graph_ or _build dependency graph_, and is the domain over which the [Bazel Query tool](/versions/8.0.1/query/guide) operates. + + + + + + +
TargetsBUILD files
diff --git a/versions/8.1.1/concepts/build-files.mdx b/versions/8.1.1/concepts/build-files.mdx index 6e745390..06216bf4 100644 --- a/versions/8.1.1/concepts/build-files.mdx +++ b/versions/8.1.1/concepts/build-files.mdx @@ -132,3 +132,10 @@ for anyone to create new rules. programming language. Libraries can depend on other libraries, and binaries and tests can depend on libraries, with the expected separate-compilation behavior. + + + + + + +
LabelsDependencies
diff --git a/versions/8.1.1/concepts/build-ref.mdx b/versions/8.1.1/concepts/build-ref.mdx index 0625e6f9..5dce01e8 100644 --- a/versions/8.1.1/concepts/build-ref.mdx +++ b/versions/8.1.1/concepts/build-ref.mdx @@ -97,3 +97,7 @@ package groups they include. The only allowed ways to refer to them are from the the `package` function; they do not generate or consume files. For more information, refer to the [`package_group` documentation](/versions/8.1.1/reference/be/functions#package_group). + + + Labels + \ No newline at end of file diff --git a/versions/8.1.1/concepts/dependencies.mdx b/versions/8.1.1/concepts/dependencies.mdx index ec900637..dcf79caa 100644 --- a/versions/8.1.1/concepts/dependencies.mdx +++ b/versions/8.1.1/concepts/dependencies.mdx @@ -337,3 +337,10 @@ filegroup( ``` You can then reference the label `my_data` as the data dependency in your test. + + + + + + +
BUILD filesVisibility
diff --git a/versions/8.1.1/concepts/labels.mdx b/versions/8.1.1/concepts/labels.mdx index 066aa383..8dd577c6 100644 --- a/versions/8.1.1/concepts/labels.mdx +++ b/versions/8.1.1/concepts/labels.mdx @@ -239,3 +239,10 @@ the build. This directed acyclic graph over targets is called the _target graph_ or _build dependency graph_, and is the domain over which the [Bazel Query tool](/versions/8.1.1/query/guide) operates. + + + + + + +
TargetsBUILD files
diff --git a/versions/8.2.1/concepts/build-files.mdx b/versions/8.2.1/concepts/build-files.mdx index 3fbbba98..b315f07b 100644 --- a/versions/8.2.1/concepts/build-files.mdx +++ b/versions/8.2.1/concepts/build-files.mdx @@ -132,3 +132,20 @@ for anyone to create new rules. programming language. Libraries can depend on other libraries, and binaries and tests can depend on libraries, with the expected separate-compilation behavior. + + + + + + +
+ + Labels + + + + Dependencies + +
diff --git a/versions/8.2.1/concepts/build-ref.mdx b/versions/8.2.1/concepts/build-ref.mdx index a6501030..9d2783cf 100644 --- a/versions/8.2.1/concepts/build-ref.mdx +++ b/versions/8.2.1/concepts/build-ref.mdx @@ -97,3 +97,7 @@ package groups they include. The only allowed ways to refer to them are from the the `package` function; they do not generate or consume files. For more information, refer to the [`package_group` documentation](/versions/8.2.1/reference/be/functions#package_group). + + + Labels + \ No newline at end of file diff --git a/versions/8.2.1/concepts/dependencies.mdx b/versions/8.2.1/concepts/dependencies.mdx index c74b28b1..9e326a7a 100644 --- a/versions/8.2.1/concepts/dependencies.mdx +++ b/versions/8.2.1/concepts/dependencies.mdx @@ -352,3 +352,21 @@ filegroup( ``` You can then reference the label `my_data` as the data dependency in your test. + + + + + + +
+ + BUILD files + + + + Visibility + +
+ diff --git a/versions/8.2.1/concepts/labels.mdx b/versions/8.2.1/concepts/labels.mdx index 37724f9b..cc5e4da0 100644 --- a/versions/8.2.1/concepts/labels.mdx +++ b/versions/8.2.1/concepts/labels.mdx @@ -243,3 +243,20 @@ the build. This directed acyclic graph over targets is called the _target graph_ or _build dependency graph_, and is the domain over which the [Bazel Query tool](/versions/8.2.1/query/guide) operates. + + + + + + +
+ + Targets + + + + BUILD files + +
diff --git a/versions/8.3.1/concepts/build-files.mdx b/versions/8.3.1/concepts/build-files.mdx index 0b4501f1..934730fb 100644 --- a/versions/8.3.1/concepts/build-files.mdx +++ b/versions/8.3.1/concepts/build-files.mdx @@ -132,3 +132,12 @@ for anyone to create new rules. programming language. Libraries can depend on other libraries, and binaries and tests can depend on libraries, with the expected separate-compilation behavior. + + + + + + +
LabelsDependencies
diff --git a/versions/8.3.1/concepts/build-ref.mdx b/versions/8.3.1/concepts/build-ref.mdx index 2dac5555..d14bae3d 100644 --- a/versions/8.3.1/concepts/build-ref.mdx +++ b/versions/8.3.1/concepts/build-ref.mdx @@ -97,3 +97,7 @@ package groups they include. The only allowed ways to refer to them are from the the `package` function; they do not generate or consume files. For more information, refer to the [`package_group` documentation](/versions/8.3.1/reference/be/functions#package_group). + + + Labels + \ No newline at end of file diff --git a/versions/8.3.1/concepts/dependencies.mdx b/versions/8.3.1/concepts/dependencies.mdx index 15af2848..19a142db 100644 --- a/versions/8.3.1/concepts/dependencies.mdx +++ b/versions/8.3.1/concepts/dependencies.mdx @@ -349,3 +349,13 @@ filegroup( ``` You can then reference the label `my_data` as the data dependency in your test. + + + + + + +
BUILD filesVisibility
+ diff --git a/versions/8.3.1/concepts/labels.mdx b/versions/8.3.1/concepts/labels.mdx index b05be33c..69ba4335 100644 --- a/versions/8.3.1/concepts/labels.mdx +++ b/versions/8.3.1/concepts/labels.mdx @@ -239,3 +239,12 @@ the build. This directed acyclic graph over targets is called the _target graph_ or _build dependency graph_, and is the domain over which the [Bazel Query tool](/versions/8.3.1/query/guide) operates. + + + + + + +
TargetsBUILD files
diff --git a/versions/8.4.2/concepts/build-files.mdx b/versions/8.4.2/concepts/build-files.mdx index db47dddf..2a8bec93 100644 --- a/versions/8.4.2/concepts/build-files.mdx +++ b/versions/8.4.2/concepts/build-files.mdx @@ -132,3 +132,10 @@ for anyone to create new rules. programming language. Libraries can depend on other libraries, and binaries and tests can depend on libraries, with the expected separate-compilation behavior. + + + + + + +
LabelsDependencies
diff --git a/versions/8.4.2/concepts/build-ref.mdx b/versions/8.4.2/concepts/build-ref.mdx index 166fe41d..4a1875b7 100644 --- a/versions/8.4.2/concepts/build-ref.mdx +++ b/versions/8.4.2/concepts/build-ref.mdx @@ -97,3 +97,7 @@ package groups they include. The only allowed ways to refer to them are from the the `package` function; they do not generate or consume files. For more information, refer to the [`package_group` documentation](/versions/8.4.2/reference/be/functions#package_group). + + + Labels + \ No newline at end of file diff --git a/versions/8.4.2/concepts/dependencies.mdx b/versions/8.4.2/concepts/dependencies.mdx index 11ebe5e6..de4279ff 100644 --- a/versions/8.4.2/concepts/dependencies.mdx +++ b/versions/8.4.2/concepts/dependencies.mdx @@ -332,3 +332,11 @@ filegroup( ``` You can then reference the label `my_data` as the data dependency in your test. + + + + + + +
BUILD filesVisibility
+ diff --git a/versions/8.4.2/concepts/labels.mdx b/versions/8.4.2/concepts/labels.mdx index 34f013f7..72601041 100644 --- a/versions/8.4.2/concepts/labels.mdx +++ b/versions/8.4.2/concepts/labels.mdx @@ -239,3 +239,10 @@ the build. This directed acyclic graph over targets is called the _target graph_ or _build dependency graph_, and is the domain over which the [Bazel Query tool](/versions/8.4.2/query/guide) operates. + + + + + + +
TargetsBUILD files
diff --git a/versions/8.5.1/concepts/build-files.mdx b/versions/8.5.1/concepts/build-files.mdx index 6a9c6680..303cfc71 100644 --- a/versions/8.5.1/concepts/build-files.mdx +++ b/versions/8.5.1/concepts/build-files.mdx @@ -132,3 +132,14 @@ for anyone to create new rules. programming language. Libraries can depend on other libraries, and binaries and tests can depend on libraries, with the expected separate-compilation behavior. + + + + + + +
+ Labels + + Dependencies +
diff --git a/versions/8.5.1/concepts/build-ref.mdx b/versions/8.5.1/concepts/build-ref.mdx index 2301173e..756f5fe1 100644 --- a/versions/8.5.1/concepts/build-ref.mdx +++ b/versions/8.5.1/concepts/build-ref.mdx @@ -97,3 +97,7 @@ package groups they include. The only allowed ways to refer to them are from the the `package` function; they do not generate or consume files. For more information, refer to the [`package_group` documentation](/versions/8.5.1/reference/be/functions#package_group). + + + Labels + \ No newline at end of file diff --git a/versions/8.5.1/concepts/dependencies.mdx b/versions/8.5.1/concepts/dependencies.mdx index 4220df4b..2a46e91f 100644 --- a/versions/8.5.1/concepts/dependencies.mdx +++ b/versions/8.5.1/concepts/dependencies.mdx @@ -352,3 +352,21 @@ filegroup( ``` You can then reference the label `my_data` as the data dependency in your test. + + + + + + +
+ + BUILD files + + + + Visibility + +
+ diff --git a/versions/8.5.1/concepts/labels.mdx b/versions/8.5.1/concepts/labels.mdx index a9a0439d..5f6bff90 100644 --- a/versions/8.5.1/concepts/labels.mdx +++ b/versions/8.5.1/concepts/labels.mdx @@ -239,3 +239,14 @@ the build. This directed acyclic graph over targets is called the _target graph_ or _build dependency graph_, and is the domain over which the [Bazel Query tool](/versions/8.5.1/query/guide) operates. + + + + + + +
+ Targets + + BUILD files +
diff --git a/versions/8.6.0/concepts/build-files.mdx b/versions/8.6.0/concepts/build-files.mdx index 09f8ae87..08b5904a 100644 --- a/versions/8.6.0/concepts/build-files.mdx +++ b/versions/8.6.0/concepts/build-files.mdx @@ -132,3 +132,18 @@ for anyone to create new rules. programming language. Libraries can depend on other libraries, and binaries and tests can depend on libraries, with the expected separate-compilation behavior. + + + + + + +
+ + Labels + + + + Dependencies + +
diff --git a/versions/8.6.0/concepts/build-ref.mdx b/versions/8.6.0/concepts/build-ref.mdx index 128daa84..3bdee30b 100644 --- a/versions/8.6.0/concepts/build-ref.mdx +++ b/versions/8.6.0/concepts/build-ref.mdx @@ -97,3 +97,7 @@ package groups they include. The only allowed ways to refer to them are from the the `package` function; they do not generate or consume files. For more information, refer to the [`package_group` documentation](/versions/8.6.0/reference/be/functions#package_group). + + + Labels + \ No newline at end of file diff --git a/versions/8.6.0/concepts/dependencies.mdx b/versions/8.6.0/concepts/dependencies.mdx index adc54f0d..b1d14626 100644 --- a/versions/8.6.0/concepts/dependencies.mdx +++ b/versions/8.6.0/concepts/dependencies.mdx @@ -366,3 +366,19 @@ filegroup( ``` You can then reference the label `my_data` as the data dependency in your test. + + + + + + +
+ + BUILD files + + + + Visibility + +
+ diff --git a/versions/8.6.0/concepts/labels.mdx b/versions/8.6.0/concepts/labels.mdx index d9d7b320..87dfe0cd 100644 --- a/versions/8.6.0/concepts/labels.mdx +++ b/versions/8.6.0/concepts/labels.mdx @@ -239,3 +239,18 @@ the build. This directed acyclic graph over targets is called the _target graph_ or _build dependency graph_, and is the domain over which the [Bazel Query tool](/versions/8.6.0/query/guide) operates. + + + + + + +
+ + Targets + + + + BUILD files + +
diff --git a/versions/9.0.0/concepts/build-files.mdx b/versions/9.0.0/concepts/build-files.mdx index 164a1b78..42e7b901 100644 --- a/versions/9.0.0/concepts/build-files.mdx +++ b/versions/9.0.0/concepts/build-files.mdx @@ -130,6 +130,13 @@ for anyone to create new rules. and binaries and tests can depend on libraries, with the expected separate-compilation behavior. + + + + + +
LabelsDependencies
+ ## File encoding `BUILD` and `.bzl` files should be encoded in UTF-8, of which ASCII is a valid diff --git a/versions/9.0.0/concepts/build-ref.mdx b/versions/9.0.0/concepts/build-ref.mdx index df9ae0e8..6c0f7d78 100644 --- a/versions/9.0.0/concepts/build-ref.mdx +++ b/versions/9.0.0/concepts/build-ref.mdx @@ -97,3 +97,7 @@ package groups they include. The only allowed ways to refer to them are from the the `package` function; they do not generate or consume files. For more information, refer to the [`package_group` documentation](/versions/9.0.0/reference/be/functions#package_group). + + + Labels + \ No newline at end of file diff --git a/versions/9.0.0/concepts/dependencies.mdx b/versions/9.0.0/concepts/dependencies.mdx index 169b0f81..218b243c 100644 --- a/versions/9.0.0/concepts/dependencies.mdx +++ b/versions/9.0.0/concepts/dependencies.mdx @@ -352,3 +352,11 @@ filegroup( ``` You can then reference the label `my_data` as the data dependency in your test. + + + + + + +
BUILD filesVisibility
+ diff --git a/versions/9.0.0/concepts/labels.mdx b/versions/9.0.0/concepts/labels.mdx index fbd95b70..38059f37 100644 --- a/versions/9.0.0/concepts/labels.mdx +++ b/versions/9.0.0/concepts/labels.mdx @@ -238,3 +238,10 @@ the build. This directed acyclic graph over targets is called the _target graph_ or _build dependency graph_, and is the domain over which the [Bazel Query tool](/versions/9.0.0/query/guide) operates. + + + + + + +
TargetsBUILD files