| commit | 1013d789de525eb8a16de941fa0d8c7fbfa1289d | [log] [tgz] |
|---|---|---|
| author | Steve Muckle <smuckle@google.com> | Thu May 28 14:05:25 2020 -0700 |
| committer | Steve Muckle <smuckle@google.com> | Tue Jun 02 15:17:04 2020 -0700 |
| tree | 49526c6ceb03feb48eac6ef03651c494da8486f1 | |
| parent | f2910972211ed07b0a6c927268d314703c4710c5 [diff] |
move module list creation outside conditionals Currently the two special-case calls to create just a module load list (as opposed to copying a set of modules and creating a module load list) are inside checks that the related board macro for the module set is not empty. While it would be incorrect to create a non-empty module load list with an empty set of modules, this error would quickly surface at runtime. More importantly, moving these out will permit refactoring this code to clean it up. Bug: 157645635 Change-Id: I199788d49072d4c59737b3ef2c75546852cf3e36
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.