From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Option for debug support in DirectFB package
Date: Tue, 9 Jun 2015 10:15:08 +0200 [thread overview]
Message-ID: <20150609101508.034c93f0@free-electrons.com> (raw)
In-Reply-To: <ea9e1bad9d8e6c95d8611537b5224ccc@openmailbox.org>
Dear C?dric Marie,
On Tue, 09 Jun 2015 09:29:00 +0200, C?dric Marie wrote:
> But then, since it is already commited, is your removal of DirectFB
> specific debug option still relevant?
Well, maybe no.
> Or should we create another global option to enable debug (i.e. traces)
> in autotools packages (and similar things in other types of packages
> when possible)?
> This is just a question, I have no personal need for this debug
> option...
A global option is a bit problematic, because we have discovered that
--enable-debug is clearly not used for the same thing in all packages.
Some packages add -Werror, some add some other funky stuff, some simply
enable debugging symbols. --enable-debug is not a standard, formalized
option with a well-defined meaning. So I don't think a global option
that applies to all autotools packages make sense here.
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2015-06-09 8:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-08 21:56 [Buildroot] Option for debug support in DirectFB package Cédric Marie
2015-06-08 22:19 ` Thomas Petazzoni
2015-06-09 7:29 ` Cédric Marie
2015-06-09 8:15 ` Thomas Petazzoni [this message]
2015-06-09 8:47 ` Cédric Marie
2015-06-08 22:27 ` Arnout Vandecappelle
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=20150609101508.034c93f0@free-electrons.com \
--to=thomas.petazzoni@free-electrons.com \
--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