commit | 432bd660dc354893dfd190d1e9a3bd7b1150d884 | [log] [tgz] |
---|---|---|
author | Steven Moreland <smoreland@google.com> | Fri May 24 21:13:15 2024 +0000 |
committer | Steven Moreland <smoreland@google.com> | Thu May 30 17:31:08 2024 +0000 |
tree | 4b13bfaaa76bf4edacaa6d018a21ccc14cfb41b9 | |
parent | bdb6b87837135a69f35f9abe28658ce2cdf179e2 [diff] |
check_elf_file: check prebuilts are aligned WARNING: two things still need to be done 1. this should probably only be enabled when PAGE_SIZE is undefined, but I'm curious what other targets break now. 2. we may need a per-prebuilt way to disable this, like some of the other settings here. For prebuilts added onto a device, we can check the page alignment matches the one declared in the build configuration. Bug: 342466032 Test: manually, by changing the script to require 64 KB alignment, I was able to see its errors on new targets. Change-Id: Ic118245e64d67204bf5fa740a3e1afb7325b34f5
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.