commit | f1e9d4f62f8cd801a7c21c97e9e679b6a5f4e4de | [log] [tgz] |
---|---|---|
author | Jae Shin <jaeshin@google.com> | Tue Jul 24 16:12:42 2018 +0900 |
committer | Jae Shin <jaeshin@google.com> | Tue Jul 24 16:12:42 2018 +0900 |
tree | b938e57e31f336c29e184970d2e73fb6f019c58a | |
parent | c4ae41b251cf2de671112341d8af55267ebaa609 [diff] |
Additionally check TARGET_IS_64_BIT for binder bitness Since TARGET_USES_64_BIT_BINDER could be not set, first check TARGET_IS_64_BIT when determining binder bitness. Test: lunch aosp_walleye-userdebug && m -j vndk, then check directory structure Bug: 111773572 Change-Id: If75d5946b38d7b5bc15798b273e0450035c8c43a
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.