Lines Matching refs:it

9 files. In simple cases Soong is able to infer it from its knowledge of Java SDK
10 libraries and the `libs` property in Android.bp, but in more complex cases it is
18 If a library is in `libs`, it usually should *not* be added to the above
21 Android.bp/Android.mk file (e.g. when it is a `java_library` rather than a
24 cases it is possible to tell the build system that the library provides a
26 deprecated in the future, and it is recommended to fix the underlying problem):
31 It is possible to disable the check on a per-module basis. When doing that it is
39 Finally, it is possible to globally disable the check:
44 The environment variable overrides the product variable, so it is possible to
45 disable the check for a product, but quickly re-enable it for a local build.
160 a long time, and the places where it's been able to be used have shrinked over
168 There is a prebuilt of it available in prebuilts/build-tools, and a make
173 it for incremental build correctness):
184 rules/actions executed within it will only have access to a limited number of
216 because it makes your build non-reproducible. It's very unlikely that your
282 This is still an active migration, so currently it still uses
284 `PRODUCT_HOST_PACKAGES`, it would trigger installation for all of the same host
314 specify which modules should be installed, effectively making it impossible to
328 identity of the user running the build, but if you do, it's available in the
336 `BUILD_NUMBER` should not be used directly in Android.mk files, as it would
337 trigger them to be re-read every time the `BUILD_NUMBER` changes (which it does
339 builds are more reproducible. If you do need it, use `BUILD_NUMBER_FROM_FILE`:
347 whenever it's run. It will not re-run your command if the build number has
387 on a `.PHONY` target, it can get quite expensive for what should be a tiny
395 have "/" in them, and real file targets do have a "/". This makes it more
407 2. The target is a real file, but it's outside the output directories. All
416 If the first target isn't intended to be a real file, then it should be marked
420 If the second (PHONY) target is a real file, it may unnecessarily be marked
437 marking it with `.PHONY`:
461 output directory could become significantly more expensive than it already can
464 If used during Android.mk files, and later tasks, it is increasingly likely
466 a single build step, and instead setting it for hundreds of thousands.
531 `LOCAL_MODULE_RELATIVE_PATH` (or `LOCAL_MODULE_PATH` if you're still using it).
623 particular variable, we'll switch it to obsolete, and any references will become
638 need an absolute variable, convert it to absolute during a rule, so that it's
655 This isn't only set by envsetup.sh, but it is modified by it. Due to that it's
656 rather easy for this to change between different shells, and it's not ideal to
661 it's preferrable to just use the path to the file itself (since you should
675 Like PATH, this isn't only set by envsetup.sh, but it is modified by it. Due to
676 that it's rather easy for this to change between different shells, and it's not