commit | fbaabab8bc6956b1441a809a7585e9e561bce8ea | [log] [tgz] |
---|---|---|
author | Steven Moreland <smoreland@google.com> | Fri Dec 13 18:57:22 2024 +0000 |
committer | Steven Moreland <smoreland@google.com> | Fri Dec 13 18:57:22 2024 +0000 |
tree | b203597559952962b9bffe7281bd7bfa521fa57c | |
parent | 7e776b902917834a481c2a8863e7ba7c0c64b621 [diff] |
Page size alignment - ignore 32-bit. For devices with PRODUCT_SHIPPING_API_LEVEL >= 36, if they are 32-bit + 64-bit, this test will create a build error. Instead, we're only enforcing the page alignment at build time for 64-bit libraries. We could track 32-bit page size or enforce them to be 4096. I would expect such a change to catch no issues, but it may also tag a large number of 32-bit firmware and other prebuilts. We also don't care about these binaries for the 16 KB page size project. So ignore 32-bit page sizes here. Bug: 383003132 Test: build Change-Id: I577fb78e3a968ceda4c071c5a12baaf8318ca479
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.