commit | 2817d304e332219a83c7c42c784e0acc6ddff8a7 | [log] [tgz] |
---|---|---|
author | Alessandro Astone <ales.astone@gmail.com> | Sun Mar 07 21:41:02 2021 +0100 |
committer | Jackeagle <jackeagle102@gmail.com> | Thu May 27 09:23:21 2021 -0400 |
tree | 4e822c7459a5cc012db5681a463cb26c9aca5915 | |
parent | b34aa5c2da2a019679999f6de12425d9c57ea568 [diff] |
build: Turn redundant path requirements error into a warning * The change I3bf5f36125167af546dd967464a56d77f2bf3a3a added the vendor.lineage.power hidl interface to the exclusion list, however the 64 bit library is only generated by 64 bit targets. This would trigger the redundant requirements check for targets like lineage_arm or lineage_x86. * There is really no need for this to be an error, so make it a warning instead. Change-Id: I3ddf9cd6a2d8b60dc0df508c2fa14877f0f54356
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.