| commit | e6bd1d2060a8b176a8fd72ec34367f6507bc9336 | [log] [tgz] |
|---|---|---|
| author | Dan Willemsen <dwillemsen@google.com> | Thu Apr 30 21:18:58 2020 -0700 |
| committer | Dan Willemsen <dwillemsen@google.com> | Fri May 01 17:43:45 2020 -0700 |
| tree | e5fad4e9710ba93493620f4dc9b774301b5f0658 | |
| parent | 1ae5abc46e9b5c1721ec725bd05c2a24d9c80479 [diff] |
Remove TARGET_PROJECT[_SYSTEM]_INCLUDES Everything should be getting device specific kernel headers from the device_kernel_headers header library these days. This does change the behavior of system libraries on devices using the VNDK -- they no longer get device-specific kernel headers by default, as we generally expect the system image to be device-independent. The few libraries that may still need this can use: LOCAL_HEADER_LIBRARIES += device_kernel_headers Test: treehugger Change-Id: I90ccb921d58b8d27dd0118a974202696e0af745f
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.