commit | ebadc969a8dd8d884bf636a2b3fd21ad082a72fe | [log] [tgz] |
---|---|---|
author | Juan Yescas <jyescas@google.com> | Thu Nov 09 11:21:14 2023 -0800 |
committer | Juan Yescas <jyescas@google.com> | Thu Nov 09 12:51:30 2023 -0800 |
tree | 4837a889ea81acd3f4b446d3b3aa60de84ee3c97 | |
parent | 2b46f4d199e7b3c8081d6988f0bdecc34831f62d [diff] |
16k: Support max-page-size alignment greater than 4096 for x86-64 To simulate 16k page size in x86-64 cuttefish, it is necessary to compile the shared libraries and binaries with max-page-size greater than 4096. Bug: 309816695 Test: source build/envsetup.sh lunch aosp_cf_x86_64_phone_pgagnostic-trunk-userdebug m Change-Id: Id8e142a5a3556f5fd30ce90eaac236dcbc1b0881
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.