| commit | 86b529a23eb8f7800024cfc37c7e691183490199 | [log] [tgz] |
|---|---|---|
| author | Tao Bao <tbao@google.com> | Wed Jun 19 17:03:37 2019 -0700 |
| committer | Tao Bao <tbao@google.com> | Tue Jun 25 11:10:55 2019 -0700 |
| tree | ae1a8428607c2507df3aee41a9230bdcfeebd386 | |
| parent | ec53f441fa759f2c39a0c363ab92b13ab328f138 [diff] |
releasetools: Make apex_utils Python 3 compatible. In order to get a Python 2 and 3 compatible re-raise behavior, this CL removes the stack traceback for the lines within apex_util module (i.e. sys.exc_info()[2]). It's not a big loss in practice, since we only have one line within the try-except block (`common.RunAndCheckOutput()`) that's no longer reported in the traceback. Using `six` module could better solve this, but only after building releasetools as python_binary_host modules where we can properly handle the module dependency. Bug: 131631303 Test: TreeHugger Test: `python -m unittest test_apex_utils` Test: `python3 -m unittest test_apex_utils` Change-Id: I0c5a72ec9fad5ff9d8c9c94d29e813e433ec2921
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.