| commit | bb73388acf41cf7e94e485dfad6e549b1710b518 | [log] [tgz] |
|---|---|---|
| author | Tao Bao <tbao@google.com> | Wed Jul 24 23:31:19 2019 -0700 |
| committer | Tao Bao <tbao@google.com> | Wed Jul 24 23:34:25 2019 -0700 |
| tree | ec3ac9b6fe6e057861dfa93c26e0539a81539b68 | |
| parent | 6722de127788be23c051b17424ae4d239da3ac6e [diff] |
releasetools: Fix the use of StringIO. Based on the actual semantics, it actually wants an in-memory _bytes_ buffer (io.BytesIO), especially when running with Python 3. This CL fixes the issue and adds a unittest. Bug: 131631303 Test: python -m unittest test_sign_target_files_apks Test: python3 -m unittest test_sign_target_files_apks Change-Id: I3fb067acc26713f1842e831225607779fd0d1b7e
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.