| commit | c92c01d1f9a21a1918dc0360480576a38f75dcd6 | [log] [tgz] |
|---|---|---|
| author | Chet Kener <Cl3Kener@gmail.com> | Fri Jan 23 11:16:04 2015 -0500 |
| committer | Jackeagle <jackeagle102@gmail.com> | Sat Dec 12 07:24:14 2020 +0100 |
| tree | 56b3bc32460d778dc374e134f50448a205c5316c | |
| parent | cfca08b80c2c375aa4319f74bc27e4a92b74ed67 [diff] |
Remove ro.kernel.android.checkjni * JNI, the Java Native Interface, provides a way for code written in the Java programming language interact with native (C/C++) code. The extended JNI checks will cause the system to run more slowly, but they can spot a variety of nasty bugs before they have a chance to cause problems. Change-Id: I7a9c8d4b5c21980950afe171c6eea363d4fa891a Signed-off-by: mydongistiny <jaysonedson@gmail.com>
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.