commit | 72222fbec9b2efd6709e263dc16bcca98f216c15 | [log] [tgz] |
---|---|---|
author | Kalesh Singh <kaleshsingh@google.com> | Tue Apr 18 14:09:07 2023 -0700 |
committer | Kalesh Singh <kaleshsingh@google.com> | Fri Apr 21 21:04:10 2023 +0000 |
tree | 5e3ddafc27b3a2a0bffdfccb477f4d35be478f11 | |
parent | 67ca3c05c743f6ce68ad3d8a15adb32a326d1009 [diff] |
16k: Add ro.product.cpu.pagesize.max property The device's max supported page size is determined by the build variable TARGET_MAX_PAGE_SIZE_SUPPORTED. Export this variable as system property for use in tests. Bug: 277360995 Test: atest -c vendor_elf_alignment_test -s <serial> Change-Id: I4f33a42de359c8119e55056f9fd9c7147c7058ec Signed-off-by: Kalesh Singh <kaleshsingh@google.com>
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.