From fa3d44f7f4dfbf2c6d49af4635231534700d90f4 Mon Sep 17 00:00:00 2001 From: Oswald Buddenhagen Date: Tue, 16 Jun 2009 09:58:55 +0200 Subject: disable stdout buffering alltogether having system-dependent bahavior is Not Nice (TM), and given that we do only printf()s of whole lines anyway, this should have no performance impact whatsoever. Reviewed-by: mariusSO --- qmake/main.cpp | 9 +++------ 1 file changed, 3 insertions(+), 6 deletions(-) diff --git a/qmake/main.cpp b/qmake/main.cpp index f311699..2295e36 100644 --- a/qmake/main.cpp +++ b/qmake/main.cpp @@ -84,14 +84,11 @@ bool qmake_setpwd(const QString &p) int runQMake(int argc, char **argv) { -#ifndef Q_OS_WIN32 // stderr is unbuffered by default, but stdout buffering depends on whether // there is a terminal attached. Buffering can make output from stderr and stdout - // appear out of sync, so force stdout to be line buffered to minimize this without - // hurting performance too much (if at all). This is particularly important for - // things like QtCreator and scripted builds. - setvbuf(stdout, (char *)NULL, _IOLBF, 0); -#endif + // appear out of sync, so force stdout to be unbuffered as well. + // This is particularly important for things like QtCreator and scripted builds. + setvbuf(stdout, (char *)NULL, _IONBF, 0); // parse command line int ret = Option::init(argc, argv); -- cgit v0.12