commit | 8c85199efecceb6345a0afa19e5268244efd957f | [log] [tgz] |
---|---|---|
author | Vilas Bhat <vilasbhat@google.com> | Fri Mar 22 20:45:45 2024 +0000 |
committer | Vilas Bhat <vilasbhat@google.com> | Fri Mar 22 20:45:45 2024 +0000 |
tree | 77a9139c1c251d1eb02dffb52dd51cd24a9e35f5 | |
parent | bd61eeecd75ec69bd3c60924f61028db73742c3b [diff] |
16k: core: Change default TARGET_MAX_PAGE_SIZE_SUPPORTED to 16384 Changing TARGET_MAX_PAGE_SIZE_SUPPORTED default from 65536 to 16384 as this would reduce the ELF alignment for files and thereby also decreasing the padding required. Although increased padding does not result in increased disk space (due to holes), it increases file metadata. Reducing ELF alignment also helps reduce page table memory as it reduces number of memory pages utilized / virtual memory address mappings. Test: lunch <target> && get_build_var TARGET_MAX_PAGE_SIZE_SUPPORTED Bug: 310232825 Change-Id: I7c6b1bb699fec8b8ecf49a0f06a79d89142e3a2b
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.