[Buildroot] Silencing the build

Fabio Porcedda fabio.porcedda at gmail.com
Fri Jul 18 08:18:26 UTC 2014


On Thu, Jul 17, 2014 at 10:29 PM, Yann E. MORIN <yann.morin.1998 at free.fr> wrote:
> Thomas, All,
>
> On 2014-07-17 20:31 +0200, Thomas Petazzoni spake thusly:
>> On Thu, 17 Jul 2014 19:40:46 +0200, Fabio Porcedda wrote:
>>
>> > > Hum, yes, but why? The entire build process is anyway very noisy, so is
>> > > there really a point in silencing specifically this part? What is the
>> > > ultimate goal you're trying to achieve here?
>> >
>> > My ultimate goal is to be able using the "-s" flags to silence all
>> > parts, because sometimes i just want to build and view only ">>> *"
>> > messages, errors, warning without anything else.
>> >
>> > As example the "toolchain-external" target already do that when the
>> > "-s" option is used.
>> >
>> > I've silenced only this part because it was easy and it's anyway an improvement.
>> >
>> > Maybe i can work on silencing other parts too if the feature is desired.
>>
>> Ok, thanks for the explanation.
>>
>> I guess we need to decide whether having a fully silent build in "make
>> -s" is a goal we should aim at. It seems like a good idea to me, but I
>> don't have a really strong opinion about this.
>>
>> What do others think about this?
>
> Here's what I use for a silent build:
>
>     brmake() {
>         make "${@}" \
>         |sed -r -e '/^.{4}>>>[[:space:]]+(.*).{5}$/!d; s//\1/;'
>     }
>
> Then calling 'brmake' instead of 'make', will get you only the >>> lines.

Nice, so i'm not the only one who likes a silent build ;-)

I think that a downside of this method is that even the stderr is
filtered as well so messages like warning or errors are filtered as
well.

> Of course, does not work if you invoke a CLI configurator, either
> directly, or as a consequence of a missing .config. I basically
> always call it with no argument, otherwise, I use plain 'make'.
>

Regards
-- 
Fabio Porcedda



More information about the buildroot mailing list