commit | 316f77ba3c62310628c783db4e78463c0784fbd6 | [log] [tgz] |
---|---|---|
author | Inseob Kim <inseob@google.com> | Thu May 23 08:59:55 2019 +0900 |
committer | Inseob Kim <inseob@google.com> | Thu Aug 08 18:46:31 2019 +0900 |
tree | f2f655dc9cc0c3c6d52c75b56e07459915634cc4 | |
parent | 69340f6885a41d347b3c55b5c12d2a746346cdf0 [diff] |
Include headers and props to VNDK snapshot For all vndk snapshot libraries, header files exported by the libraries will be included to the snapshot. Android.bp will contain necessary information to link against/install vndk snapshot libraires: export_include_dirs, export_system_include_dirs, export_flags, and relative_install_path. Bug: 132818174 Test: 1) VNDK_SNAPSHOT_BUILD_ARTIFACTS=true \ development/vndk/snapshot/build.sh Test: 2) development/vndk/snasphot/update.py Test: 3) see contents of Android.bp and include directories Change-Id: I3ed179b613ca51f7854dc819783a962a56b973eb
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.