summaryrefslogtreecommitdiffstats
path: root/bitbake/lib
diff options
context:
space:
mode:
authorRichard Purdie <richard.purdie@linuxfoundation.org>2014-03-26 16:56:08 +0000
committerRichard Purdie <richard.purdie@linuxfoundation.org>2014-03-27 10:17:20 +0000
commit6f29f7d371c4188d656414646b70cfa86244228b (patch)
tree23443a94674b437a086c3e0396f24d9ec4682a97 /bitbake/lib
parentcf9777339453d0920bbd07e512b448ce3a5c1168 (diff)
downloadpoky-6f29f7d371c4188d656414646b70cfa86244228b.tar.gz
bitbake: knotty: Ensure the progress bar shows on stdout
I can understand why some programs would want the progress on stderr so that real output can be captured on stdout. This is confusing for bitbake since we don't show a progress bar at all in non-interactive cases. Therefore make sure the progress bar goes to stdout, not the stderr default. (Bitbake rev: 0529aa9966df5c56b07affe865efce18852efe5a) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'bitbake/lib')
-rw-r--r--bitbake/lib/bb/ui/knotty.py2
1 files changed, 1 insertions, 1 deletions
diff --git a/bitbake/lib/bb/ui/knotty.py b/bitbake/lib/bb/ui/knotty.py
index 009653c038..31c2dbbcfc 100644
--- a/bitbake/lib/bb/ui/knotty.py
+++ b/bitbake/lib/bb/ui/knotty.py
@@ -49,7 +49,7 @@ class BBProgress(progressbar.ProgressBar):
49 self._resize_default = signal.getsignal(signal.SIGWINCH) 49 self._resize_default = signal.getsignal(signal.SIGWINCH)
50 except: 50 except:
51 self._resize_default = None 51 self._resize_default = None
52 progressbar.ProgressBar.__init__(self, maxval, [self.msg + ": "] + widgets) 52 progressbar.ProgressBar.__init__(self, maxval, [self.msg + ": "] + widgets, fd=sys.stdout)
53 53
54 def _handle_resize(self, signum, frame): 54 def _handle_resize(self, signum, frame):
55 progressbar.ProgressBar._handle_resize(self, signum, frame) 55 progressbar.ProgressBar._handle_resize(self, signum, frame)