Lines Matching +full:ninja +full:- +full:bin
3 ## Dexpreopt starts enforcing `<uses-library>` checks (for Java modules)
7 the `<uses-library>` tags in the manifest. Since the build system does not have
19 properties, and Soong should be able to infer the `<uses-library>` tag. But
25 `<uses-library>` with a given name (however, this is discouraged and will be
31 It is possible to disable the check on a per-module basis. When doing that it is
45 disable the check for a product, but quickly re-enable it for a local build.
110 To temporarily turn the build-time restriction off, use
121 is no other non-optional assignments having the same name. For example, the
126 Note that the order between the optional and the non-optional assignments
149 * `<partition>/bin/*`
168 There is a prebuilt of it available in prebuilts/build-tools, and a make
183 With `ALLOW_NINJA_ENV=false` (soon to be the default), ninja, and all the
185 environment variables. Ninja does not track when environment variables change
216 because it makes your build non-reproducible. It's very unlikely that your
222 been a mistake in the Android.mk -- assuming that `LOCAL_C_INCLUDES` (which is
255 and `android.hardware.boot@1.0-impl.recovery` into recovery image
270 and would be over-building with both. So `PRODUCT_PACKAGES` will be changing to
286 necessary in `PRODUCT_*PACKAGES`, and tended to be over-built (especially the
287 32-bit variants).
290 for host modules, error when there's a host-only module in `PRODUCT_PACKAGES`,
304 ## Windows cross-compiles no longer supported in Android.mk
312 modules to specify that they should always be installed on `-eng`, or `-eng`
313 and `-userdebug` builds. This conflicted with the ability for products to
321 `build/make/target/product/base_system.mk`, but for device-specific modules
332 of `android-build`. The real value is available as `BUILD_HOSTNAME`.
337 trigger them to be re-read every time the `BUILD_NUMBER` changes (which it does
343 mytool --build_number $(BUILD_NUMBER_FROM_FILE) -o $@
347 whenever it's run. It will not re-run your command if the build number has
351 ## `DIST_DIR`, `dist_goal`, and `dist-for-goals` {#dist}
354 files (or other build tasks). Always use `dist-for-goals` instead, which takes
361 $(call dist-for-goals,foo,bar/baz)
372 $(call dist-for-goals,foo,bar/baz:logs/foo.log)
383 `.PHONY`-marked targets are often used as shortcuts to provide "friendly" names
386 aliases or one-off user-requested operations, but if real builds steps depend
400 ...mk:42: warning: writing to readonly directory: "kernel-modules"
436 incrementals, over-specifying dependencies is likely a better option than
440 out/target/.../zImage: $(sort $(shell find -L $(KERNEL_SRCDIR)))
446 -- without custom checks, Make doesn't rebuild objects when CFLAGS change, etc.
458 steps -- we're looking at triggering build steps to be invalidated if the set
478 rm -rf $@
488 rm -rf $@
494 rm -rf $@
527 extra '/' or '../' being inserted can cause problems -- and not just build
537 LOCAL_MODULE := ver1/code.bin
543 LOCAL_MODULE := ver2/code.bin
553 LOCAL_MODULE := ver1_code.bin
554 LOCAL_MODULE_STEM := code.bin
560 LOCAL_MODULE := ver2_code.bin
561 LOCAL_MODULE_STEM := code.bin
573 requirements](https://docs.bazel.build/versions/master/build-ref.html#name) for
574 target names. Valid characters are `a-z`, `A-Z`, `0-9`, and the special
575 characters `_.+-=,@~`. This currently applies to `LOCAL_PACKAGE_NAME`,
600 is to use tools checked into the tree -- either as prebuilts, or building them
629 |--------------------------------------------------------------|----------------------|
639 not expanded into the generated ninja file:
643 export PRODUCT_OUT=$$(cd $(PRODUCT_OUT); pwd); cd my/src/path; ./gen.sh -o $${PRODUCT_OUT}/gen.img
670 PATH=my/path:$$PATH myscript -o $@
691 $(TARGET): myscript.py $(sort $(shell find my/python/lib -name '*.py'))
692 PYTHONPATH=my/python/lib:$$PYTHONPATH myscript.py -o $@
696 Specify Framework Compatibility Matrix Version in device manifest by adding a `target-level`
698 is 26 or 27, you can add `"target-level"="1"` to your device manifest instead.