commit | 9340a673cda4e6558cf65454cf7406b8fe7cb3ed | [log] [tgz] |
---|---|---|
author | Jooyung Han <jooyung@google.com> | Tue May 14 16:44:52 2019 +0900 |
committer | Jooyung Han <jooyung@google.com> | Sat May 25 02:06:08 2019 +0900 |
tree | c3b01ca23f58a1a716d53bd52aa33dfaae6bb3a4 | |
parent | 8614d0181c39574e943d0615871991f933e1f803 [diff] |
make: Add support to skip current VNDK install You can get a system.img without current VNDK libs. This may help when you want a smaller system.img given that the image will be used with a specific version (not current) of vendor image. Bug: 132140714 Test: m TARGET_SKIP_CURRENT_VNDK=true && see if current VNDK is not installed Change-Id: Ie0815e6dd6ce2f861b6c42e637da4bb146320673
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.