From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] CMake and VERBOSE variable
Date: Tue, 1 Sep 2015 00:34:49 +0200 [thread overview]
Message-ID: <55E4D689.30103@mind.be> (raw)
In-Reply-To: <55E449F9.90407@openmailbox.org>
On 31-08-15 14:35, C?dric Marie wrote:
> Hi,
>
> Le 31/08/2015 09:28, Thomas Petazzoni a ?crit :
>> Arnout, C?dric,
>>
>> On Sun, 23 Aug 2015 01:10:39 +0200, Arnout Vandecappelle wrote:
>>
>>> For autotools it depends a lot on the version. Relatively recent automake (at
>>> least 1.15) has the V=0/1 option, but it defaults to 1 I think.
>>
>> It actually depends on how AM_SILENT_RULES is used:
>>
>> * If it's not used, then the build is verbose, and V=0/1 has no effect.
>>
>> * If AM_SILENT_RULES is used, with no special argument, then it
>> defaults to verbose (V=1), but can be made quiet by passing V=0
>>
>> * If AM_SILENT_RULES([yes]) is used, then it defaults to quiet (V=0)
>> and can be made verbose by passing V=1.
>
>
> So I think the best way to manage it is to be explicit: "V=0" when nothing is
> specified (because we want the default to be silent), and "V=1" when V=1 from
> the command line.
Actually, we want the default to be the package build system's default, I
think. So do nothing when nothing is specified, and add V=1 when V=1 is specified.
> In worst case, it is not taken into account.
> Otherwise, it is correctly managed, whatever the default setting of AM_SILENT_RULE.
>
> NB: I said that the behaviour was kept unchanged, but in fact there is one case
> that seems to be better handled with my modification: when AM_SILENT_RULES is
> used without argument (i.e. the default is verbose). Now we turn it to quiet by
> forcing explicit V=0.
Perhaps we could do that when V=0 is passed explicitly on buildroot's top-level
make.
BTW, this stuff should also be tested from an output directory and with a
non-022 umask.
Regards,
Arnout
>
>
--
Arnout Vandecappelle arnout at mind be
Senior Embedded Software Architect +32-16-286500
Essensium/Mind http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint: 7493 020B C7E3 8618 8DEC 222C 82EB F404 F9AC 0DDF
next prev parent reply other threads:[~2015-08-31 22:34 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-09 7:54 [Buildroot] CMake and VERBOSE variable Cédric Marie
2015-06-10 22:00 ` Arnout Vandecappelle
2015-06-11 7:37 ` Cédric Marie
2015-06-11 20:05 ` Arnout Vandecappelle
2015-06-18 8:29 ` Cédric Marie
2015-06-21 19:23 ` Arnout Vandecappelle
2015-06-22 9:47 ` Cédric Marie
2015-06-22 10:50 ` Samuel Martin
2015-06-22 11:26 ` Cédric Marie
2015-06-22 11:57 ` Samuel Martin
2015-06-22 14:22 ` Cédric Marie
2015-08-20 13:04 ` Cédric Marie
2015-08-22 23:10 ` Arnout Vandecappelle
2015-08-30 20:27 ` Cédric Marie
2015-08-31 7:28 ` Thomas Petazzoni
2015-08-31 12:35 ` Cédric Marie
2015-08-31 22:34 ` Arnout Vandecappelle [this message]
2015-09-05 21:18 ` Cédric Marie
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=55E4D689.30103@mind.be \
--to=arnout@mind.be \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.