commit | bbdfbdad508cd15013cca676c8724e3fc6a5f6fc | [log] [tgz] |
---|---|---|
author | Steve Muckle <smuckle@google.com> | Fri Jun 26 16:39:34 2020 -0700 |
committer | Steve Muckle <smuckle@google.com> | Fri Jun 26 16:39:34 2020 -0700 |
tree | e25a29a97d7ec1542df9a201feb59ea19ffb9ac3 | |
parent | b829269aa1628d24c55c8591fff6a00402ef6504 [diff] |
use first kernel when generating kernel configs file If multiple kernels are defined for a build, use the first one when generating the kernel config file. Bug: 159975506 Change-Id: Ia136264eb0d0b544bf0685bc22e600de187a9a9b
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.