| commit | 04434739a2f65e1b0230fe8e7d8abd7586ed3a76 | [log] [tgz] |
|---|---|---|
| author | Elliott Hughes <enh@google.com> | Tue Jan 10 22:59:40 2023 +0000 |
| committer | Elliott Hughes <enh@google.com> | Fri Jan 13 00:41:38 2023 +0000 |
| tree | a295af34c44d57ac73a0de0d240ed366c2cb4f11 | |
| parent | e61203da9cc00d0b93f62ba4d8b04f05a2a2f4b5 [diff] |
zipalign/ziptime: use ftello()/fseeko(). Even if we were shipping 64-bit Windows host tools (which we still aren't), this would still be a bug. Windows is LLP64 instead of LP64, so the long that ftell()/fseek() uses isn't big enough for a 64-bit off_t. Test: treehugger Change-Id: I4e24afe811ff9b7d5696887cc5ee92e54e4a3b76
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.