Lines Matching refs:modules

5 declarative descriptions of modules to build.
59   This is commonly used to reference `filegroup` modules, whose output files
109 ### Defaults modules
111 A defaults module can be used to repeat the same properties in multiple modules.
131 specification of the dependencies among them in the form of modules.
138 The modules in a package's `Android.bp` and included files are part of the module.
161 E.g. The following will set the default visibility for all the modules defined in the package and
202 modules defined in the Android.bp files in the `device/google/bonito/` tree have
203 unique names. However, there may be modules with the same names outside
237 is searched for "_name_" (in other words, only the modules not belonging to an
239 `soong_namespaces` allows to specify where to look for modules . For instance,
260 #### Referencing modules in makefiles
275 the same modules via PRODUCT_SOONG_NAMESPACES may cause Make failure. For
283 used by other packages. Modules are always visible to other modules declared
295 * `["//some/package:__pkg__", "//other/package:__pkg__"]`: Only modules in
300 module and must be used verbatim. It represents all of the modules in the
302 * `["//project:__subpackages__", "//other:__subpackages__"]`: Only modules in
368 The tool converts variables, modules, comments, and some conditionals, but any
374 * Android.mk files often have multiple modules with the same name (for example
378 The androidmk converter will produce multiple conflicting modules, which must
416 When converting vendor modules that contain conditionals, simple conditionals
418 modules that describe the module types, variables and possible values:
496 `soong_config_module_type` modules will work best when used to wrap defaults
497 modules (`cc_defaults`, `java_defaults`, etc.), which can then be referenced
498 by all of the vendor's other modules using the normal namespace and visibility