Lines Matching refs:that

9 file, generate that file into `$OUT_DIR` during the build, fail the build
11 generated script, etc) to explicitly copy that file from the output into the
23 as that could trigger extra rebuilds when a source directory is moved.
25 Assume that the source directory is `$PWD`. If a script is going to change
27 prefer to do that in the script.
32 Don't assume that `$OUT_DIR` is `out`. The source and output trees are very
36 Don't assume that `$OUT_DIR` is under `$PWD`, users can set it to a relative path
50   up so that space isn't wasted, but the files are there when necessary.
66 the exported headers reference a library that you link to, use
80 Sometimes there are headers that have header-only sections, but also define
83 re-export that header library from the existing library. This will prevent
85 or accidentally not linking to a library that's actually necessary.
90 are using headers that shouldn't be available to them -- usually due to the
100 * It moves more information next to the values -- that the array of strings
105   inheritable groups that can be selected with a single property.
116 file formats. You can verify that the dependencies are read correctly with:
124 change in dependencies as something that would invalidate an action -- the
128 so that any additions or removals from those directories would trigger your
189 completely by putting the `PRODUCT_PACKAGES` entry in a product makefile that
233 by products that use soc_a should contain:
241 used to partition a set of modules so that they are built only when the
283 be written in Go that can implement additional features for specific module