| commit | 2f7e11ef27bc00108088eb2b0f5a5d9cc605afdd | [log] [tgz] |
|---|---|---|
| author | Regnier, Philippe <philippe.regnier@intel.com> | Wed May 22 10:10:57 2019 +0800 |
| committer | Xihua Chen <xihua.chen@intel.com> | Thu Jul 11 17:05:17 2019 +0800 |
| tree | 0e5d096185f78b277c5547450e03ea431239b7fd | |
| parent | 40b5340a94bc3199a28b99e5d1c997442f5322e0 [diff] |
logging: set stdout and stderr to None in some cases For very long processes, we might want to keep stdout and stderr by default to None. So no redirection will occur in the child process as explained in: https://docs.python.org/2/library/subprocess.html That will result in the child process stdin and stderr to be same than in common.py and avoid to have the logs blocked during the child process execution and flushed only when child process terminates. Since the logs are continously displayed, it allows to easily confirm that the process is not blocked. Bug: 133380588 Test: generate iota & Check that the logs are not blocked. Change-Id: I6d6cb56547bf3a4a4334dfa22b6b2b05d2c36a5e Signed-off-by: Regnier, Philippe <philippe.regnier@intel.com>
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.