Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Cédric Marie" <cedric.marie@openmailbox.org>
To: buildroot@busybox.net
Subject: [Buildroot] Option for debug support in DirectFB package
Date: Mon, 08 Jun 2015 23:56:09 +0200	[thread overview]
Message-ID: <55760F79.8080501@openmailbox.org> (raw)

Hi,

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.

-- 
C?dric

             reply	other threads:[~2015-06-08 21:56 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-08 21:56 Cédric Marie [this message]
2015-06-08 22:19 ` [Buildroot] Option for debug support in DirectFB package Thomas Petazzoni
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=55760F79.8080501@openmailbox.org \
    --to=cedric.marie@openmailbox.org \
    --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