Lines Matching refs:of

7 System properties for each of the partition is supposed to be set via following
84 Note that this behavior is different from the previous behavior of preferring
114 There is a prebuilt of it available in prebuilts/build-tools, and a make
130 rules/actions executed within it will only have access to a limited number of
155 Neither of these cases are supported by Soong, and will produce errors when
169 relative to the top of the source tree) acts like `LOCAL_SRC_FILES` (which is
194 and install the recovery variant of boot control HAL modules into recovery
196 crosshatch for example of this:
206 ## Deprecation of `BUILD_*` module types
223   property of the target, not the host.
230 `PRODUCT_HOST_PACKAGES`, it would trigger installation for all of the same host
243 source file by appending `.arm` to the end of the filename in
272 `USER` will soon be `nobody` in many cases due to the addition of a sandbox
273 around the Android build. Most of the time you shouldn't need to know the
274 identity of the user running the build, but if you do, it's available in the
278 of `android-build`. The real value is available as `BUILD_HOSTNAME`.
301 a PHONY goal, and a list of files to copy to `$DIST_DIR`. Whenever `dist` is
303 or as a dependency of something on the command line), that file will be copied
314 Instead of specifying just a file, a destination name can be specified,
325 There are several new warnings/errors meant to ensure the proper use of
326 `.PHONY` targets in order to improve the speed and reliability of incremental
349 This warning will show up for one of two reasons:
377 We recommend to build these outside of Android, and deliver prebuilts into the
378 Android tree instead of decreasing the speed and reliability of the incremental
381 In cases where that's not desired, to preserve the speed of Android
390 For reliability, many of these other build systems do not guarantee the same
391 level of incremental build assurances as the Android Build is attempting to do
393 In order to fix this, our recommendation is to do clean builds for each of
405 of environment variables they can access changes. If device specific
412 a single build step, and instead setting it for hundreds of thousands.
414 It is not recommended to just move the environment variable setting outside of
533 To start with, this includes replacing the $PATH with our own directory of
534 tools, mirroring that of the host PATH.  The only difference so far is the
535 removal of the host GCC tools. Anything that is not explicitly in the
557 including a majority of our automated build systems, do not do so. Make will
562 Many of these variables also include absolute path names, which we'd like to
563 keep out of the generated files, so that you don't need to do a full rebuild if
574 | instead of                                                   | use                  |
582 All of the make variables may be relative paths from the current directory, or
595 root of the source tree, so this can just be replaced with '.' (which is what
606 rule reference a particular binary that's part of the source tree or outputs,
611 layers of unchangable scripts/binaries. In that case, be sure to add the
627 that no longer needs PYTHONPATH. See fontchain_lint for examples of this:
660 the makefile system. If you need one of them, you'll have to set up your own