Lines Matching refs:it

51   `module` is the name of a module that produces output files, and it expands to
135 package includes all files in its directory, plus all subdirectories beneath it, except those which
154 in the same package directory it is highly recommended that the `package` module (if required) is
214 A module name's **scope** is the smallest namespace containing it. Suppose a
231 is a namespace called "_scope_", then verifies it contains a "_name_" module and
232 uses it. Soong verifies there is only one "_name_" in "_scope_" at the beginning
233 when it parses Android.bp files.
235 A **local reference** has "_name_" form, and resolving it involves looking for a
270 an explicit namespace, it can be referenced from a makefile only after after the
277 namespaces will cause Make failure because it will see two targets for the
313 `//visibility:public` for now. It is an error if it is used in a module.
321 in `vendor/`, e.g. a module in `libcore` cannot declare that it is visible to
322 say `vendor/google`, instead it must make itself visible to all packages within
325 If a module does not specify the `visibility` property then it uses the
329 it will use the `default_visibility` of its closest ancestor package for which
335 The `visibility` property has no effect on a defaults module although it does
336 apply to any non-defaults module that uses it. To set the visibility of a
340 Once the build has been completely switched over to soong it is possible that a
466 the file where it is defined, or can be imported into another file with: