commit | dd5401713c038e368497dbaa87978bd042fa7f56 | [log] [tgz] |
---|---|---|
author | Justin Yun <justinyun@google.com> | Mon Jan 20 07:39:41 2020 +0000 |
committer | Justin Yun <justinyun@google.com> | Mon Jan 20 07:39:41 2020 +0000 |
tree | fe7fd2f0ebf44c691f5618adb9986ae9a2110333 | |
parent | 4e7e76fe5a19996ad02f7260ef81c780b41f1a99 [diff] |
Revert "Linktype check for native:product" This reverts commit 4e7e76fe5a19996ad02f7260ef81c780b41f1a99. Reason for revert: build breaks (bid: 6147225) and postsubmit test fails. There are some modules that have both "product_specific: true" and "vendor_available: true", which tags the module as "native:product" unintentionally. We need to clean up these cases first and revisit this CL. Bug: 146620523 Bug: 147987741 Change-Id: Ib07543235d72a135b6b732aaa909c147d2df832b
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.