commit | bf086436b0003f77861f1d6cc7e8d589a3009393 | [log] [tgz] |
---|---|---|
author | Colin Cross <ccross@android.com> | Thu Oct 10 12:50:51 2019 -0700 |
committer | Colin Cross <ccross@android.com> | Thu Oct 10 12:52:13 2019 -0700 |
tree | 5b24b6532168f0241554a7184bc6daaf674c9248 | |
parent | 42b2b54c2b3961f7a25098e044e3c8261779e712 [diff] |
Remove stray ZIPALIGN_PAGE_ALIGN_FLAGS Iae26e4676c29c68fa3f76187512c82786bfa0522 removed the definition of ZIPALIGN_PAGE_ALIGN_FLAGS in favor of always using the -p flag, but left accidentaly left one usage. Replace it with -p. Bug: 141212627 Test: m checkbuild Change-Id: Ica69d9195426f8f30039da211ed1a0ad5dffe8e8
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.