commit | 6c37c172c66e5b3f322fc28b16190282766ab21f | [log] [tgz] |
---|---|---|
author | Bowgo Tsai <bowgotsai@google.com> | Fri Feb 05 18:01:15 2021 +0800 |
committer | Bowgo Tsai <bowgotsai@google.com> | Fri Feb 05 18:14:34 2021 +0800 |
tree | 17835c00e253e09ff9274733427d2d2d11d62694 | |
parent | 250a0420eaff086067c4137c082a8bf528116f57 [diff] |
Adding repack_bootimg into otatools.zip repack_bootimg is useful to add files into a ramdisk, then repack a boot.img. Note that mkbootimg, unpack_bootimg, lz4, minigzip, etc., that repack_bootimg depends are already in otatools.zip. Bug: 174443192 Test: `m otatools-package`, unzip $OUT/otatools.zip, export $PATH with ./otatools/bin and checks unpack_bootimg can run Change-Id: Id4fbf2076b50522b95ab46dfeb1e2b7115d6606d
This is the Makefile-based portion of the Android Build System.
For documentation on how to run a build, see Usage.txt
For a list of behavioral changes useful for Android.mk writers see Changes.md
For an outdated reference on Android.mk files, see build-system.html. Our Android.mk files look similar, but are entirely different from the Android.mk files used by the NDK build system. When searching for documentation elsewhere, ensure that it is for the platform build system -- most are not.
This Makefile-based system is in the process of being replaced with Soong, a new build system written in Go. During the transition, all of these makefiles are read by Kati, and generate a ninja file instead of being executed directly. That's combined with a ninja file read by Soong so that the build graph of the two systems can be combined and run as one.