Google Git
Sign in
android / platform / build / 7a70db721b052d6b43a652d9b01244bcc37d05eb
commit7a70db721b052d6b43a652d9b01244bcc37d05eb[log] [tgz]
authorColin Cross <ccross@android.com>Mon Nov 15 10:58:31 2021 -0800
committerMartin Stjernholm <mast@google.com>Tue Nov 16 16:29:45 2021 +0000
tree5e4df99eae558ce6410f43f477bd34a07be4719e
parent5616fb1dc47d87b640c8fd805b36ef037243d81b [diff]
Always default to 1.9 for host java modules in Android.mk files

Host modules shouldn't use the logic for device modules to determine
the java language version to use, always default to 1.9.

Cherry-pick from https://r.android.com/1892956 - this may be necessary
in sc-mainline-prod when it switches to prebuilt SDKs (b/204189791).

Bug: 202761304
Test: presubmits
Change-Id: I268dd34d887db4646e188858c7f2aedc30966856
Merged-In: I268dd34d887db4646e188858c7f2aedc30966856
1 file changed
tree: 5e4df99eae558ce6410f43f477bd34a07be4719e
  1. common/
  2. core/
  3. packaging/
  4. target/
  5. tests/
  6. tools/
  7. .gitignore
  8. Android.bp
  9. banchanHelp.sh
  10. buildspec.mk.default
  11. Changes.md
  12. CleanSpec.mk
  13. Deprecation.md
  14. envsetup.sh
  15. help.sh
  16. METADATA
  17. navbar.md
  18. OWNERS
  19. PREUPLOAD.cfg
  20. rbesetup.sh
  21. README.md
  22. tapasHelp.sh
  23. Usage.txt
README.md

Android Make Build System

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.