Gitiles
Code Review Sign In
review.shift-gmbh.com / SHIFTPHONES / android_build / 9ff5fbb02382506ee213910e210d2411c87b1246
commit9ff5fbb02382506ee213910e210d2411c87b1246[log] [tgz]
authorChristopher Ferris <cferris@google.com>Tue Apr 23 17:22:00 2024 -0700
committerChristopher Ferris <cferris@google.com>Thu Apr 25 16:46:35 2024 -0700
tree756b901b744ed6b710579f144a3ccb1d0ef807a0
parent83f8fb1643a7520a5c4a8404bbb83a9aba9b374d [diff]
Add MALLOC_LOW_MEMORY as synonym for MALLOC_SVELTE.

The MALLOC_SVELTE variable name is confusing, so add a new variable
name called MALLOC_LOW_MEMORY. Still support MALLOC_SVELTE.
Also, support the change of Malloc_not_svelte to Malloc_low_memory.

Test: Verified scudo config is used by default.
Test: Verfified Android GO config uses the jemalloc low memory config.
Change-Id: I2606205da746d8ab20e29884c7dcb5a77add51e4
3 files changed
tree: 756b901b744ed6b710579f144a3ccb1d0ef807a0
  1. ci/
  2. common/
  3. core/
  4. packaging/
  5. target/
  6. teams/
  7. tests/
  8. tools/
  9. .gitignore
  10. Android.bp
  11. banchanHelp.sh
  12. buildspec.mk.default
  13. Changes.md
  14. CleanSpec.mk
  15. cogsetup.sh
  16. Deprecation.md
  17. envsetup.sh
  18. help.sh
  19. METADATA
  20. navbar.md
  21. OWNERS
  22. PREUPLOAD.cfg
  23. rbesetup.sh
  24. README.md
  25. shell_utils.sh
  26. tapasHelp.sh
  27. 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.