Lines Matching refs:be

17 future, though there will be some level of exceptions for tools like `distcc`
43 instead.  This can be problematic in a number of ways:
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
101   will be used as a list of sources is useful, both for humans and automated
105   inheritable groups that can be selected with a single property.
125 command line would need to change, or one of the inputs would need to be newer
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
147 them to be installed when necessary. Adding unnecessary libraries into
148 `PRODUCT_PACKAGES` will force them to always be installed, wasting space.
154 code less testable, as it must be built with each combination of flags to
155 be tested.
159 Conditionally compiling a module can generally be replaced with conditional
188 If the condition was on a type of board or product, it can often be dropped
195 for compilation via a conditional, the implementations can sometimes be renamed
198 For example, the name of the gralloc HAL module can be overridden by the
240 In cases where the names cannot be made unique a `soong_namespace` should be
249 module name.  These can be renamed to a fixed name.
251 For example, the name of the gralloc HAL module can be overridden by the
282 As a last resort, if the conditional cannot be removed, a Soong plugin can
283 be written in Go that can implement additional features for specific module
286 plugins should be used only when absolutely required.