Yifan Hong 2dcc1dcf9c ota_from_target_files: include metadata when odm / product is changed.
When odm is changed, device manifest/matrices should be included.
When product is changed, framework manifest/matrices should be included.

Bug: 130714844
Bug: 126770403
Test: build with odm and product VINTF metadata

Change-Id: I49c8083e0e7185ae7b96047d68f1f624b1113dfc
Merged-In: I49c8083e0e7185ae7b96047d68f1f624b1113dfc
2019-04-24 16:28:49 -07:00
2018-12-17 13:46:17 -08:00
2019-04-24 16:28:48 -07:00
2019-04-24 16:28:48 -07:00
2015-07-23 13:18:47 -07:00
2019-04-23 16:24:29 +08:00
2018-08-20 10:44:59 -07:00
2019-03-18 10:21:15 -07:00
2018-01-08 15:26:16 -08:00
2018-07-14 09:32:13 -07:00

Android Make Build System

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.

Description
No description provided
Readme 104 MiB
Languages
Makefile 32.1%
Python 31.1%
Go 13.7%
Rust 7.7%
Java 5.2%
Other 10.1%