| commit | dcb5ef1333aa4e0fc987b68e27a24b1c63ce2f63 | [log] [tgz] |
|---|---|---|
| author | Anton Hansson <hansson@google.com> | Mon Oct 15 11:35:15 2018 +0100 |
| committer | Anton Hansson <hansson@google.com> | Wed Oct 17 16:40:29 2018 +0100 |
| tree | c8ff0e1375b9e25f967f9c9c1cc9b110f997427c | |
| parent | 7f758720f617403f230795aa5255e5817f31a84a [diff] |
Re-submit "Add trailing slash to mainline path claims." With a workaround for preopt files that get installed into an unknown path. The BoardConfig defines whether the files go in /system_other, so allow that. This reverts commit 46bf4b510cf3492eefaab8e7e36b5807a7c75aec. Test: lunch mainline_arm64-userdebug; m nothing Change-Id: Ia75670eb6e3730ad0ff17f5b81954b69f6cab22b
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.