| commit | b95d02eac9fd6f88402cdb3a215ee6af2d6d458c | [log] [tgz] |
|---|---|---|
| author | Yifan Hong <elsk@google.com> | Fri Nov 13 18:33:01 2020 -0800 |
| committer | Yifan Hong <elsk@google.com> | Fri Nov 13 18:45:03 2020 -0800 |
| tree | b4c613754b3960d7e68deb30c4e50b4d4353543d | |
| parent | 72e78f21b25cff7541acd9d94941a1c180b34ed3 [diff] |
Pass kernel release file to check_vintf. check_vintf now accepts a file that contains the full kernel release string as the first half of --kernel. Use it. With this patch, BOARD_KERNEL_VERSION can be a full kernel release string like 5.4.42-something, or 5.4.42-android12-0-something. The content of target_files/META/kernel_version.txt also contains the full kernel release, not just the kernel version. Bug: 161317193 Test: m check-vintf-all Change-Id: I3b52639f557532077894d9356c745c16b41dd91c
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.