| commit | 1d7f51da6f0a8690b2d5418d6cdcca95e3fbfd4b | [log] [tgz] |
|---|---|---|
| author | Dan Albert <danalbert@google.com> | Fri Mar 31 21:39:53 2023 +0000 |
| committer | Dan Albert <danalbert@google.com> | Tue Apr 04 21:28:51 2023 +0000 |
| tree | dce82a6891f7c631b988f46bef7098f02d492735 | |
| parent | 00670e0c0349344b220c5348cb1df246f10e64bd [diff] |
Adapt to rearranged NDK sysroot. Soong didn't have any explicit references to these paths because it depends directly on the modules, but the make side of the build still needs to construct these paths explicitly. I removed a bunch of dead code that made the fix less obvious while I was here. Bug: None Test: treehugger Change-Id: I1a283a3bc98a94fc5481c869b3b0a4eacf69d859
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.