commit | b32e1479efd7e22cad46361c577e8a12e0851ad9 | [log] [tgz] |
---|---|---|
author | Lev Rumyantsev <levarum@google.com> | Tue Sep 21 13:10:00 2021 -0700 |
committer | Lev Rumyantsev <levarum@google.com> | Tue Sep 21 15:01:08 2021 -0700 |
tree | 25b90f5bfdabd38704b5da6735716aa5a97e0591 | |
parent | b9306ac477d4d2be5cfd079f56b583bb0009e687 [diff] |
Make native.bridge property overridable When a device uses native bridge, it may be included in the system image, so overriding by vendor/build.prop is not an option. Example of overriding can be seen here: ag/15881132 Test: build cf_x86_64_phone-userdebug with native-bridge and launch, observe 1. ro.dalvik.vm.native.bridge=native_bridge.so moved from vendor/build.prop to system/build.prop 2. the prop is correctly set at runtime 3. translated apps work Bug: 197153442 Change-Id: I6cd566dd4e0fac181e309cb7f282d086de09075b
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.