commit | 791378cda108a145f8e390e36d617c1c5c56b6a4 | [log] [tgz] |
---|---|---|
author | cfig <yuyezhong@gmail.com> | Sun Feb 07 17:01:26 2021 +0800 |
committer | cfig <yuyezhong@gmail.com> | Sun Feb 07 17:05:53 2021 +0800 |
tree | 3d541dcca2f4d9a503b8675b8d545f4c85d2cebb | |
parent | 289a0ffdaf453af38295c77b71341250ea67ed28 [diff] |
extract_kernel: make it py2/py3 compatible use py3 for AOSP build, while the script itself can be executed under py2/py3 environment directly. TEST: extract info from Pixel 4 kernel Change-Id: I00db6dabb1ff93f0758017a666c476816caefae7
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.