From: Pavel Machek <pavel@ucw.cz>
To: Bernd Petrovitsch <bernd@firmix.at>
Cc: Oleg Verych <olecom@flower.upol.cz>,
Andrew Morton <akpm@linux-foundation.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
kbuild devel list <linux-kbuild@vger.kernel.org>
Subject: Re: coloring stdout && stderr, small kbuild example
Date: Sat, 12 Apr 2008 20:32:18 +0200 [thread overview]
Message-ID: <20080412183218.GD4492@ucw.cz> (raw)
In-Reply-To: <1207754040.6860.7.camel@tara.firmix.at>
Hi!
> > Those boring never-ending builds...
> >
> > Can some dualCPU power be spent, if building is interactive (i.e. sent to
> > terminal), to have them a bit colored?
> >
> > My last rant about "colored printk()" led away from kernel developers
> > and their solutions. But now, let me share something.
>
> I don't know if it's of any use for you but there is already
> *) color-make - http://bre.klaki.net/programs/colormake/ - and
> *) color-gcc - http://schlueters.de/colorgcc.html -
> out there.
icecc seems to do the coloring, too...
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
next prev parent reply other threads:[~2008-04-12 19:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-09 15:02 coloring stdout && stderr, small kbuild example Oleg Verych
2008-04-09 15:14 ` Bernd Petrovitsch
2008-04-09 15:40 ` Oleg Verych
2008-04-09 17:39 ` Oleg Verych
2008-04-12 18:32 ` Pavel Machek [this message]
2008-04-13 15:27 ` lide: linux ide, just concept idea (Re: coloring stdout && stderr, small kbuild example) Oleg Verych
2008-04-09 15:39 ` coloring stdout && stderr, small kbuild example Oleg Verych
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20080412183218.GD4492@ucw.cz \
--to=pavel@ucw.cz \
--cc=akpm@linux-foundation.org \
--cc=bernd@firmix.at \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=olecom@flower.upol.cz \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox