| commit | 69f7191d5d223fecc0556261ea31bdaec701f957 | [log] [tgz] |
|---|---|---|
| author | Justin Yun <justinyun@google.com> | Mon Mar 08 19:31:37 2021 +0900 |
| committer | Justin Yun <justinyun@google.com> | Mon Mar 15 18:17:35 2021 +0900 |
| tree | fae347c41bf99bc4ec770c6f4f37af4fabd0dedd | |
| parent | 4d71d704961694cff93131874c8786583bddfcf6 [diff] |
Define __ANDROID_VENDOR__ and __ANDROID_PRODUCT__ __ANDROID_VNDK__ is defined for the modules that are able to use the VNDK libraries. As both product and vendor variants define __ANDROID_VNDK__, we don't know if a module is built for vendor or product on build time. __ANDROID_VENDOR__ and __ANDROID_PRODUCT__ macros can be used to specify the image-variant-dependent codes. Bug: 180646847 Test: m nothing Change-Id: I9a37607b1e1e4e16eab02fb6c96d1a92158c96b8
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.