From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] directfb: add an option for debugging support
Date: Fri, 12 Jun 2015 00:24:21 +0200 [thread overview]
Message-ID: <557A0A95.7020206@mind.be> (raw)
In-Reply-To: <5579FB8D.1020509@openmailbox.org>
On 06/11/15 23:20, C?dric Marie wrote:
> Hi,
>
> Le 11/06/2015 22:32, Arnout Vandecappelle a ?crit :
>> Yes, but I was in fact mainly talking about the help text of the new option.
>
> Oops, sorry.
> But I suppose I shouldn't give so much details in the help text, as in the
> commit message.
> What do you think is important to mention?
>
> Here is a proposal, feel free to comment/modify:
>
> Compile DirectFB with debugging support. It provides functions to print debug
> information, for DirectFB as well as external DirectFB drivers.
> When disabled, DirectFB has got no debug feature at all, and the directory that
When disabled, DirectFB does not print any debug information. The drivers will
be installed to and loaded from /usr/lib/directfb-<version>-pure instead of
/usr/lib/directfb-<version>-.
> contains the internal libraries is suffixed with -pure
> (/usr/lib/directfb-<version>-pure/).
>
>
> NB: I'm not really satisfied with "internal libraries", but I can't find the
> right expression for that. It contains gfx drivers, but not only...
gfx drivers, input drivers, window systems drivers, ... I think it's drivers
:-) Only interfaces doesn't fit.
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: 7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F
next prev parent reply other threads:[~2015-06-11 22:24 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-09 20:43 [Buildroot] [PATCH] directfb: add an option for debugging support Cédric Marie
2015-06-10 21:45 ` Arnout Vandecappelle
2015-06-11 12:58 ` Cédric Marie
2015-06-11 20:32 ` Arnout Vandecappelle
2015-06-11 21:20 ` Cédric Marie
2015-06-11 22:24 ` Arnout Vandecappelle [this message]
2015-06-12 7:09 ` Cédric Marie
-- strict thread matches above, loose matches on Subject: below --
2015-06-15 20:02 Cédric Marie
2015-06-17 22:10 ` Arnout Vandecappelle
2015-06-21 7:38 ` Thomas Petazzoni
2015-06-14 20:51 Cédric Marie
2015-06-14 22:07 ` Arnout Vandecappelle
2015-06-15 6:33 ` Cédric Marie
2015-06-16 21:15 ` Arnout Vandecappelle
2015-06-09 20:32 Cédric Marie
2015-06-09 20:45 ` 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=557A0A95.7020206@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox