| commit | 32e70da517b0b18c6ef77b7ea1fee73c6033604a | [log] [tgz] |
|---|---|---|
| author | Anton Hansson <hansson@google.com> | Mon Jun 18 15:08:42 2018 +0100 |
| committer | Anton Hansson <hansson@google.com> | Tue Jun 19 10:40:01 2018 +0000 |
| tree | 7285fb14816492faba826e34dd34fafe3230ce41 | |
| parent | 500fccebf75572701730082de13108bded5d2739 [diff] |
Remove embedded.mk The common mk files form a long chain of generic sounding names that don't make much sense. For instance, embedded, base, core_minimal, core and core_base all inherit each other, but there's no logical ordering of these names. The common mks will be split based on destination partition, which will create many new files. Merging some of the common ones before this split keeps the total number of mks under control. There are only 2 products inheriting this mk excluding base.mk (which has over 300 descendants). The other levels in the hierarchy all have multiple device categories rooted at them (e.g. wearables from base.mk, tvs and cars from core_minimal.mk), but embedded.mk has not which makes it a compelling target to remove. Bug: 80410283 Test: diff products variables with multiproduct_kati Change-Id: I35c05973dfefefb7a31686476215386b8b89a557 Merged-In: I35c05973dfefefb7a31686476215386b8b89a557 Merged-In: I2e25032645c87f084f911e14fade16bc802ff457
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.