From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 3/3] sdl2: Add KMS/DRM(experimental) video driver support
Date: Tue, 26 Sep 2017 21:42:13 +0200 [thread overview]
Message-ID: <20170926214213.03f191eb@windsurf.home> (raw)
In-Reply-To: <0c84c541-fe77-0f6f-bea5-ce4f88097fab@mind.be>
Hello,
On Tue, 26 Sep 2017 21:36:40 +0200, Arnout Vandecappelle wrote:
> XORG7 is a special case, we never select it (and we assume it's obvious that
> you need X to be able to use X stuff). But if you look at e.g.
> BR2_PACKAGE_SDL2_X11, it selects BR2_PACKAGE_XLIB_LIBX11 and
> BR2_PACKAGE_XLIB_LIBXEXT rather than depending on them.
>
> BR2_PACKAGE_DIRECTFB should indeed be selected instead of depended on. That's
> historical accident, because sdl2 was largely copied from sdl, and sdl had this
> construct since 2009 when there were no clear rules yet about select/depend.
For sdl2, it would be useful to look at the review discussion. I'm
wondering if I didn't suggest to have a "depends on" for DirectFB, just
for the sake of having something consistent between the different
graphics backends. I don't remember.
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2017-09-26 19:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-26 14:47 [Buildroot] [PATCH 1/3] sdl2: Bump version to 2.0.6 Olivier Schonken
2017-09-26 14:47 ` [Buildroot] [PATCH 2/3] sdl2: Remove patches that were merged upstream Olivier Schonken
2017-09-26 15:06 ` Thomas Petazzoni
2017-09-26 14:47 ` [Buildroot] [PATCH 3/3] sdl2: Add KMS/DRM(experimental) video driver support Olivier Schonken
2017-09-26 15:07 ` Thomas Petazzoni
2017-09-26 15:10 ` Olivier Schonken
2017-09-26 19:36 ` Arnout Vandecappelle
2017-09-26 19:42 ` Thomas Petazzoni [this message]
2017-09-26 19:50 ` 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=20170926214213.03f191eb@windsurf.home \
--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