Gitiles
Code Review Sign In
gerrit.omnirom.org / android_build / d4e6add5b06d7a9f70bd4a081e2a462931c326c0
commitd4e6add5b06d7a9f70bd4a081e2a462931c326c0[log] [tgz]
authorVilas Bhat <vilasbhat@google.com>Thu Mar 21 23:50:34 2024 +0000
committerVilas Bhat <vilasbhat@google.com>Mon Mar 25 18:11:39 2024 +0000
treeb23a2d2699e4e46b6119958f66bb13197cf6550c
parent8c85199efecceb6345a0afa19e5268244efd957f [diff]
16k: core: Add defaults for TARGET_MAX_PAGE_SIZE_SUPPORTED

This refactors existing validation logic to do the following:
- Default ELF alignment to 4096 for non-(arm64/x86_64) targets.
- Default ELF alignment to 4096 if VSR_VENDOR_API_LEVEL < 34.

Test: lunch <target> && get_build_var TARGET_MAX_PAGE_SIZE_SUPPORTED
Bug: 310232825
Change-Id: Ia1548d74c9f92b70a80cb65cc6ed35d4c77edcd2
1 file changed
tree: b23a2d2699e4e46b6119958f66bb13197cf6550c
  1. ci/
  2. common/
  3. core/
  4. packaging/
  5. target/
  6. teams/
  7. tests/
  8. tools/
  9. .gitignore
  10. banchanHelp.sh
  11. buildspec.mk.default
  12. Changes.md
  13. CleanSpec.mk
  14. cogsetup.sh
  15. Deprecation.md
  16. envsetup.sh
  17. help.sh
  18. METADATA
  19. navbar.md
  20. OWNERS
  21. PREUPLOAD.cfg
  22. rbesetup.sh
  23. README.md
  24. shell_utils.sh
  25. tapasHelp.sh
  26. 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.