Lines Matching refs:package

130 The build is organized into packages where each package is a collection of related files and a
133 A package is defined as a directory containing a file named `Android.bp`, residing beneath the
135 package includes all files in its directory, plus all subdirectories beneath it, except those which
138 The modules in a package's `Android.bp` and included files are part of the module.
142 `my/app/data` is not a package, but a directory belonging to package `my/app`.
150 This is based on the Bazel package concept.
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
154 in the same package directory it is highly recommended that the `package` module (if required) is
157 Unlike most module type `package` does not have a `name` property. Instead the name is set to the
158 name of the package, e.g. if the package is in `top/intermediate/package` then the package name is
159 `//top/intermediate/package`.
161 E.g. The following will set the default visibility for all the modules defined in the package and
163 the same `.bp` file as the `package` module) to be visible to all the subpackages by default.
166 package {
201 `device/google/bonito` package the module names are unique, that is, all the
222 namespace for a module may be different from module's package name: `libfoo`
224 `device/my/display/lib` package.
284 in the same package. This is based on the Bazel visibility mechanism.
290 * `["//visibility:private"]`: Only rules in the module's package (not its
295 * `["//some/package:__pkg__", "//other/package:__pkg__"]`: Only modules in
296 `some/package` and `other/package` (defined in `some/package/*.bp` and
297 `other/package/*.bp`) have access to this module. Note that sub-packages do not
298 have access to the rule; for example, `//some/package/foo:bar` or
299 `//other/package/testing:bla` wouldn't have access. `__pkg__` is a special
301 package.
309 where `//project` is the module's package, e.g. using `[":__subpackages__"]` in
326 `default_visibility` property of the `package` module in the module's package.
328 If the `default_visibility` property is not set for the module's package then
329 it will use the `default_visibility` of its closest ancestor package for which
338 not to be confused with the `default_visibility` property on the package module.