Lines Matching refs:to

5 Never write to the source directory during the build, always write to
6 `$OUT_DIR`. We expect to enforce this in the future.
8 If you want to verify / provide an update to a checked in generated source
10 asking the user to run a command (either a straight command, checked in script,
11 generated script, etc) to explicitly copy that file from the output into the
16 Never access the network during the build. We expect to enforce this in the
25 Assume that the source directory is `$PWD`. If a script is going to change
26 directories and needs to convert an input from a relative to absolute path,
27 prefer to do that in the script.
30 it difficult to reproduce builds on other machines.
36 Don't assume that `$OUT_DIR` is under `$PWD`, users can set it to a relative path
41 Don't use `$(shell)` to write files, create symlinks, etc. We expect to
46   down build startup, but it can also trigger more build steps to run than are
48 * It's no longer possible for a stripped-down product configuration to opt-out
49   of these created files. It's better to have actual rules and dependencies set
59 removed. They've been switched from using `-isystem` to `-I` already, and are
63 access to the headers automatically if you link to the associated code.
66 the exported headers reference a library that you link to, use
69 to re-export the necessary headers to your users.
73 supported in Soong. You may need to either move your module definition up a
74 directory (for example, if you have ./src/ and ./include/, you probably want to
78 Prefer to use header libraries (`BUILD_HEADER_LIBRARY`/ `cc_library_headers`)
81 interfaces to a library. Prefer to split those header-only sections out to a
85 or accidentally not linking to a library that's actually necessary.
88 Eventually we'd like to remove `LOCAL_C_INCLUDES`, though significant cleanup
89 will be required first. This will be necessary to detect cases where modules
90 are using headers that shouldn't be available to them -- usually due to the
98 it's better to use defaults modules like `cc_defaults`, `java_defaults`, etc.
100 * It moves more information next to the values -- that the array of strings
111 * Android.bp: Just add them to the `out` list in genrule
112 * Custom Soong Plugin: Add to `Outputs` or `ImplicitOutputs`
122 Prefer to list input files on the command line, otherwise we may not know to
125 command line would need to change, or one of the inputs would need to be newer
127 may need to add the the directories to your dependency list or dependency file,
129 tool to be re-run. That can be more expensive than necessary though, since many
131 README could trigger the directory's timestamp to be updated.
134 need to know which files will be created before any inputs are read, since we
140 *.srcjar files, and will extract them before passing them on to the compiler.
144 Most libraries aren't necessary to include in `PRODUCT_PACKAGES`, unless
147 them to be installed when necessary. Adding unnecessary libraries into
148 `PRODUCT_PACKAGES` will force them to always be installed, wasting space.
153 of build combinations, leading to more build breakages.  It also makes the
154 code less testable, as it must be built with each combination of flags to
196 to unique values.
232 Then to select the correct gralloc implementation, a product makefile inherited
241 used to partition a set of modules so that they are built only when the
249 module name.  These can be renamed to a fixed name.
268 Then to select the correct gralloc implementation, a product makefile should
278 The preferred solution is to convert the conditional to runtime, either by
284 types.  Soong plugins are inherently tightly coupled to the build system