Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] support/scripts/mkmakefile: Silent wrapper
Date: Thu, 1 Nov 2018 21:44:41 +0100	[thread overview]
Message-ID: <20181101204441.GW28575@scaer> (raw)
In-Reply-To: <20181026112621.8146-1-serj.kalichev@gmail.com>

Serj, All,

On 2018-10-26 14:26 +0300, Serj Kalichev spake thusly:
>  Suppose we use Makefile wrapper and build
>  project out of buildroot tree (with O=...). The commands like "make
>  busybox-all-external-deps" will output the string "uname 022 && make ..." to
>  stdout before the usefull information. It pollutes stdout. In the same time
>  if we use the same command in the buildroot source-tree then we don't get the
>  additional output. Some external scripts can analyze output of make and
>  additional output can break them. This patch make wrapper silent.
>  
>  Sorry for the previous ugly-formatted patch.

Do not put personal messages like that in the commit log. You may put
them after the three-dash line...

> Signed-off-by: Serj Kalichev <serj.kalichev@gmail.com>
> ---

... here.

>  support/scripts/mkmakefile | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/support/scripts/mkmakefile b/support/scripts/mkmakefile
> index 37162a3173..3b1a9f8774 100755
> --- a/support/scripts/mkmakefile
> +++ b/support/scripts/mkmakefile
> @@ -33,7 +33,7 @@ MAKEFLAGS += --no-print-directory
>  all	:= \$(filter-out Makefile,\$(MAKECMDGOALS))
>  
>  _all:
> -	umask 0022 && \$(MAKE) \$(MAKEARGS) \$(all)
> +	@umask 0022 && \$(MAKE) \$(MAKEARGS) \$(all)

I actually prefer when I can see the path of Buildroot. Since I can use
many Buildroot trees to do tests, I do want to check that I am indeed
using the correct one.

However, I understand that it is weird that the in-tree and out-of-tree
do not print the same stuff, and that can be confusing.

After discussing this on IRC with Thomas, we think it would be nice if
we could mimick what the kernel currently does:
    https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/scripts/mkmakefile

The default would be to be silent (what you expect), while still
allowing people like me to turn on the verbose mode when needed.

Care to look into that, please?

In the mean time, I've marked your patch as "changes requested" in
patchwork. Thanks!

Regards,
Yann E. MORIN.

>  Makefile:;
>  
> -- 
> 2.17.1
> 
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot

-- 
.-----------------.--------------------.------------------.--------------------.
|  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___               |
| +33 223 225 172 `------------.-------:  X  AGAINST      |  \e/  There is no  |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v   conspiracy.  |
'------------------------------^-------^------------------^--------------------'

  reply	other threads:[~2018-11-01 20:44 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-26 11:26 [Buildroot] [PATCH 1/1] support/scripts/mkmakefile: Silent wrapper Serj Kalichev
2018-11-01 20:44 ` Yann E. MORIN [this message]
2018-11-02 11:36   ` Serj Kalichev
2018-11-02 11:29 ` [Buildroot] [PATCH v2 1/1] support/scripts/mkmakefile: Wrapper is silent by default Serj Kalichev
2018-11-02 14:20   ` Yann E. MORIN
2018-11-02 20:29   ` Thomas Petazzoni
2018-11-14 22:26   ` Peter Korsgaard

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=20181101204441.GW28575@scaer \
    --to=yann.morin.1998@free.fr \
    --cc=buildroot@busybox.net \
    /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