Google Git
Sign in
android / platform / build / b3e9fc2219
commitb3e9fc2219f689d1f5bc27a020913e6289e66231[log] [tgz]
authorSzuWei Lin <szuweilin@google.com>Wed Jul 03 17:45:47 2019 +0800
committerSzuWei Lin <szuweilin@google.com>Tue Jul 16 16:53:12 2019 +0800
tree0a1f1d0660a2156ad3a8bc6d0b2eba92cff159d5
parent2b4828a56494c69d4c531baa6f48ba5af121febd [diff]
Add default LMK properties to GSI

These LMK properties are product properties. The configuration will
be absent when GSI is installed as GSI doesn't mount the product
partition. Without these settings, some CTS test cases could
fail due to an aggressive LMK.

The patch puts these properties in GSI as default values.

Bug: 136212765
Bug: 134460917
Test: `run cts -m CtsFileSystemTestCases`, all pass
Change-Id: I6fde8db51debcb9bb269aece3a3e4c7e5bb991f6
Merged-In: I6fde8db51debcb9bb269aece3a3e4c7e5bb991f6
(cherry picked from commit 9547929af43eeb48e4f766daeb822d8d89416691)
2 files changed
tree: 0a1f1d0660a2156ad3a8bc6d0b2eba92cff159d5
  1. common/
  2. core/
  3. packaging/
  4. target/
  5. tests/
  6. tools/
  7. .gitignore
  8. buildspec.mk.default
  9. Changes.md
  10. CleanSpec.mk
  11. Deprecation.md
  12. envsetup.sh
  13. help.sh
  14. navbar.md
  15. OWNERS
  16. README.md
  17. tapasHelp.sh
  18. 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.