Lines Matching refs:be

16 to [Bazel BUILD files](https://www.bazel.io/versions/master/docs/be/overview.html)
33 Every module must have a `name` property, and the value must be unique across
78 can be appended to with a += assignment, but only before they have been
104 Strings, lists of strings, and maps can be appended using the `+` operator.
105 Integers can be summed up using the `+` operator. Appending a map produces the
111 A defaults module can be used to repeat the same properties in multiple modules.
152 The `package` module type allows information to be specified about a package. Only a single
153 `package` module can be specified per package and in the case where there are multiple `.bp` files
163 the same `.bp` file as the `package` module) to be visible to all the subpackages by default.
173 A module `libfoo` can be referenced by its name
203 unique names. However, there may be modules with the same names outside
222 namespace for a module may be different from module's package name: `libfoo`
269 be referenced from a makefile without additional effort. If a module belongs to
270 an explicit namespace, it can be referenced from a makefile only after after the
282 The `visibility` property on a module controls whether the module can be
288 Each rule in the property must be in one of the following forms:
293 creating module. Can only be used at the beginning of a list of visibility
300 module and must be used verbatim. It represents all of the modules in the
316 be combined with any other visibility specifications, except
332 If no `default_visibility` property can be found then the module uses the
338 not to be confused with the `default_visibility` property on the package module.
341 global refactoring will be done to change this to `//visibility:private` at
343 property will be updated to have
344 `default_visibility = [//visibility:legacy_public]` added. It will then be the
369 custom Makefile rules, complex conditionals or extra includes must be converted
377 be built in multiple variants, for example by adding `host_supported: true`.
379 be resolved by hand to a single module with any differences inside
390 property.  When building the module one of the properties in the map will be
411 be built.  When building for x86 the `generic.cpp` and 'x86.cpp' sources will
412 be built.
417 can be supported through Soong config variables using `soong_config_*`
442 The values of the variables can be set from a product's `BoardConfig.mk` file:
454 The `acme_cc_defaults` module type can be used anywhere after the definition in
455 the file where it is defined, or can be imported into another file with:
497 modules (`cc_defaults`, `java_defaults`, etc.), which can then be referenced
544 Could not attach to pid 593: this could be caused by a kernel