commit | 07c71ac1b9fc5b36a09a7cd3fe33939e73b684c4 | [log] [tgz] |
---|---|---|
author | Kelvin Zhang <zhangkelvin@google.com> | Thu Feb 17 21:46:21 2022 -0800 |
committer | Kelvin Zhang <zhangkelvin@google.com> | Thu Feb 17 21:46:21 2022 -0800 |
tree | 9578c5f93999eaedbbc861f9b12a2e5593709e6c | |
parent | 42ab8287546bc07217039643e4e277f1242c17a5 [diff] |
Remove catch + sys.exit idiom This is bad, python already prints exceptino message and exit with non-zero code when an exception is raised, no need to catch the exception just to print it. In addition, printing an exception does not print stacktrace, so catch + sys.exit provide less information than python's default behavior. Test: th Change-Id: If6cf2e34d4ebc9f7d172063b4396bf4377dad447
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.