From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Carlos Rafael Giani <dv@pseudoterminal.org>,
openembedded-core@lists.openembedded.org
Subject: Re: Why are verbose makefiles enabled by default in cmake bbclass ?
Date: Fri, 19 Aug 2016 15:43:55 +0100 [thread overview]
Message-ID: <1471617835.16712.39.camel@linuxfoundation.org> (raw)
In-Reply-To: <c1f61bbb-02ac-2ae8-9016-55a00ff71a15@pseudoterminal.org>
On Fri, 2016-08-19 at 16:10 +0200, Carlos Rafael Giani wrote:
> Hello,
>
> in a project, I'd like to disable verbose makefiles (the bbclass sets
> CMAKE_VERBOSE_MAKEFILE to 1), since the log output becomes very
> large,
> and finding compiler errors becomes more difficult. I think there is
> no
> problem in overriding the default in my recipe. However, I wonder if
> there was a specific reason for setting CMAKE_VERBOSE_MAKEFILE to 1
> in
> the cmake.bbclass, or if this was just preference. Any ideas?
People tend to report errors based on the log files and its tedious to
have to ask them to reproduce the error after having to turn on verbose
output. We do this in a few places to aid bug reporting.
Cheers,
Richard
prev parent reply other threads:[~2016-08-19 14:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-19 14:10 Why are verbose makefiles enabled by default in cmake bbclass ? Carlos Rafael Giani
2016-08-19 14:43 ` Richard Purdie [this message]
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=1471617835.16712.39.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=dv@pseudoterminal.org \
--cc=openembedded-core@lists.openembedded.org \
/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