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 00:19:53 +0200 [thread overview]
Message-ID: <20150609001953.1c241187@free-electrons.com> (raw)
In-Reply-To: <55760F79.8080501@openmailbox.org>
Dear C?dric Marie,
On Mon, 08 Jun 2015 23:56:09 +0200, C?dric Marie wrote:
> DirectFB provides two configure options for debug:
> * --enable-debug (default is no)
> * --enable-debug-support (default is yes)
> The first one enables verbose mode in DirectFB, while the second one
> only provide the functions to print debug information, that might be
> used by an external DirectFB driver.
>
> When these options are both disabled, the installation path is suffixed
> with -pure (i.e. /usr/lib/directfb-x.y.z-pure instead of
> /usr/lib/directfb-x.y.z).
>
> Buildroot only gives the possibility to enable/disable the first one
> (with BR2_PACKAGE_DIRECTFB_DEBUG).
>
> Some external DirectFB driver, when compiled in release mode, would
> expect debug support to be disabled, and would install in the -pure
> suffixed directory.
>
> Therefore it would be helpful:
> - either to have another option for debug support (and debug option
> would depend on debug support option, in Config.in)
> - or to disable debug support when debug is disabled: the two options
> would always be forced to have the same value.
>
> I believe the first solution is better, but let me know what you
> think... I can provide the patch if you agree with the suggestion.
>
> That would also prevent DirectFB to compile some useless features
> in release mode.
I am not sure I've made up my mind yet specifically about your
question, but two informations:
* BR2_PACKAGE_DIRECTFB_DEBUG will most likely be removed, as part of
a patch series I have to bump the entire DirectFB stack. See:
http://git.free-electrons.com/users/thomas-petazzoni/buildroot/log/?h=directfb-bump
* --enable-debug / --disable-debug used to be passed to all autotools
packages, depending on the state of the BR2_ENABLE_DEBUG option.
This is no longer the case since commit
http://git.buildroot.net/buildroot/commit/?id=0552a367dbdc27a211daaac3359d81dd537e384f.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2015-06-08 22:19 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 [this message]
2015-06-09 7:29 ` Cédric Marie
2015-06-09 8:15 ` Thomas Petazzoni
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=20150609001953.1c241187@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