Lines Matching refs:that

8 access to the manifest contents, that information must be present in the build
24 cases it is possible to tell the build system that the library provides a
31 It is possible to disable the check on a per-module basis. When doing that it is
100 In that case, the final value is determined at runtime. The precedence is
126 Note that the order between the optional and the non-optional assignments
131 Optional assignments can be duplicated and in that case their order matters.
138 Note that this behavior is different from the previous behavior of preferring
146 ELF prebuilts in `PRODUCT_COPY_FILES` that are installed into these paths are an
169 variable `M4` that contains the path.
189 Kati and Soong can safely use environment variables, so the expectation is that
190 you'd embed any environment variables that you need to use within the command
205 There's now a `BUILD_BROKEN_OUTSIDE_INCLUDE_DIRS` variable, that when set, will
216 because it makes your build non-reproducible. It's very unlikely that your
221 This is the new check that has been added. In every case I've found, this has
222 been a mistake in the Android.mk -- assuming that `LOCAL_C_INCLUDES` (which is
266 Previously, adding a module to `PRODUCT_PACKAGES` that supported both the host
276 * `PRODUCT_HOST_PACKAGES` does not have `_ENG`/`_DEBUG` variants, as that's a
283 `PRODUCT_PACKAGES` to make installation decisions, but verifies that if we used
301 files to be split out into a separate static library that chooses `arm` over
306 Modules that build for Windows (our only `HOST_CROSS` OS currently) must now be
312 modules to specify that they should always be installed on `-eng`, or `-eng`
315 build a stripped down product configuration that did not include those modules.
338 on every build server build). If possible, just remove the use so that your
346 That will expand out to a subshell that will read the current `BUILD_NUMBER`
357 or as a dependency of something on the command line), that file will be copied
394 Between this warning and the next, we're requiring that `.PHONY` targets do not
425 One common pattern (mostly outside AOSP) that we've seen hit these warning is
435 In cases where that's not desired, to preserve the speed of Android
465 that they are being used incorrectly. Attempting to change the environment for
470 We expect to limit the environment variables that the build respects in the
567 You just need to make sure that any other references (`PRODUCT_PACKAGES`,
584 build. This will help ensure that build results are reproducible across
588 tools, mirroring that of the host PATH.  The only difference so far is the
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
605 to be used (with logging). Beware that GCC didn't work well with the interposer
613 This means that relying on environment variables only set up in envsetup.sh will
617 keep out of the generated files, so that you don't need to do a full rebuild if
620 To fix this, we're marking the variables that are set in envsetup.sh as
638 need an absolute variable, convert it to absolute during a rule, so that it's
648 In Android.mk files, you can always assume that the current directory is the
655 This isn't only set by envsetup.sh, but it is modified by it. Due to that it's
660 rule reference a particular binary that's part of the source tree or outputs,
662 already be adding that as a dependency).
665 layers of unchangable scripts/binaries. In that case, be sure to add the
676 that it's rather easy for this to change between different shells, and it's not
681 that no longer needs PYTHONPATH. See fontchain_lint for examples of this: