| commit | de94650a0761c6cd7f3914d2a81fe5672183398f | [log] [tgz] |
|---|---|---|
| author | Mark Salyzyn <salyzyn@google.com> | Fri Feb 01 17:58:57 2019 -0800 |
| committer | android-build-merger <android-build-merger@google.com> | Fri Feb 01 17:58:57 2019 -0800 |
| tree | 55194498f23e67847198bb0b7088ba15cf9471be | |
| parent | 0fae759a19f6b28a3a944cd63b66380acea8c531 [diff] | |
| parent | 127c3f4342a708f0ebfa7dec10098f02f7ae1bb3 [diff] |
Merge "dynamic partitions: round partitions to BOARD_SUPER_PARTITION_ALIGNMENT" am: 76f2628654 am: 7007227f80 am: 127c3f4342 Change-Id: I5dd6d8a4c84f91fd360e8463181bd35a5cde8ade
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.