| commit | a2578b28ab604ab65cf9c3f3df93d54077d1e41b | [log] [tgz] |
|---|---|---|
| author | Ken Sun <kensun@google.com> | Mon Oct 03 03:12:41 2022 +0000 |
| committer | Ken Sun <kensun@google.com> | Mon Oct 03 03:12:41 2022 +0000 |
| tree | 9f6272568adb64f030a1749f11fc3d6efbb4d70c | |
| parent | 6568b77dfb872883dec02c14d5e9ad1460a26ace [diff] |
Revert "Use the toolchain from JDK 17" Revert "Use the toolchain from JDK 17" Revert submission 2164342-use-jdk17 Reason for revert: DroidMonitor-triggered revert due to breakage b/250426490 Reverted Changes: Ib1a24e7ea:Update path for libjli.so I3375bd4e4:Use the toolchain from JDK 17 I9183e5511:Use the toolchain from JDK 17 Change-Id: Ic72662dab2e57a60272b0a82606a17974efcd982
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.