| commit | c6024abe995e38f8f87459f168e8600db353340e | [log] [tgz] |
|---|---|---|
| author | Cole Faust <colefaust@google.com> | Tue Apr 26 11:08:19 2022 -0700 |
| committer | Cole Faust <colefaust@google.com> | Tue Apr 26 11:12:46 2022 -0700 |
| tree | 1f03fe8f2a0ccd2f9ddd4bd3330713968c931c2f | |
| parent | 5f6235e580ccff5de80abdc0eecb9469d394a295 [diff] |
Send trace logs to stderr instead of stdout Stdout gets redirected to a makefile that is ingested by the rest of the build system. The trace outputs were being mixed up with the rest of the output, making them hard to read. In addition, some of the trace output wasn't commented out, so it was defining make rules. Fixes: 230495885 Test: Manually Change-Id: I02f9038cd89598fc1c1561bf4bf2997ac090d9e9
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.