Lines Matching refs:not

7 the `<uses-library>` tags in the manifest. Since the build system does not have
18 If a library is in `libs`, it usually should *not* be added to the above
87 ### Duplication is not allowed within a partition
95 not an error:
161 the last several releases. Equivalent functionality is not available in Soong.
166 ## `m4` is not available on `$PATH`
185 environment variables. Ninja does not track when environment variables change
187 is not safe with incremental builds.
276 * `PRODUCT_HOST_PACKAGES` does not have `_ENG`/`_DEBUG` variants, as that's a
277   property of the target, not the host.
278 * `PRODUCT_HOST_PACKAGES` does not support `LOCAL_MODULE_OVERRIDES`.
285 packages. This check ignores shared libraries, as those are not normally
300 Soong does not support this uncommonly used behavior, instead expecting those
315 build a stripped down product configuration that did not include those modules.
336 `BUILD_NUMBER` should not be used directly in Android.mk files, as it would
347 whenever it's run. It will not re-run your command if the build number has
394 Between this warning and the next, we're requiring that `.PHONY` targets do not
409    otherwise `m clean` is unable to clean the build, and future builds may not
418 example, as we require `.PHONY` targets not to have '/' in them.
435 In cases where that's not desired, to preserve the speed of Android
444 For reliability, many of these other build systems do not guarantee the same
450 you're not trying to actively debug the kernel.
457 Device specific configuration should not be able to affect common core build
468 It is not recommended to just move the environment variable setting outside of
472 into the build, just not to every build step)
527 extra '/' or '../' being inserted can cause problems -- and not just build
589 removal of the host GCC tools. Anything that is not explicitly in the
594 contains all the common tools in use in many builds. Anything not in that list
606 used for logging, so this may not help in all cases.
610 It is not required to source envsetup.sh before running a build. Many scripts,
611 including a majority of our automated build systems, do not do so. Make will
639 not expanded into the generated ninja file:
656 rather easy for this to change between different shells, and it's not ideal to
664 Depending on the rule, passing the file path itself may not be feasible due to
676 that it's rather easy for this to change between different shells, and it's not