From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] package/mesa3d: vulkan with x11 needs dri3
Date: Thu, 23 Aug 2018 13:23:57 +0200 [thread overview]
Message-ID: <20180823132357.1dd3a730@windsurf> (raw)
In-Reply-To: <20180823102029.GE9365@scaer>
Hello,
On Thu, 23 Aug 2018 12:20:29 +0200, Yann E. MORIN wrote:
> > Doesn't this requires a bit more rework to be clean ?
>
> Yes, I'll have a further look by the end of the day. I've marked it as
> Changes Requested.
>
> To be hnest, the whole of mesa3d may need a complete overhaul I think.
> Theree dubious constructs here and there, like:
>
> config BR2_PACKAGE_MESA3D_DRI_DRIVER
> bool
> select BR2_PACKAGE_MESA3D_DRIVER
> select BR2_PACKAGE_XLIB_LIBXSHMFENCE if \
> (BR2_PACKAGE_XORG7 && BR2_TOOLCHAIN_HAS_SYNC_4)
>
> So now I wonder if we shouldn't have something akin to this for Vulkan.
>
> Really, mesa3d has become quite a nest of snakes. It's hard to follow
> and understand the dependencies between each config options...
Yes, the mesa3d package is quite complicated. But I believe this (at
least partially) reflects that the mesa3d configuration itself is quite
complicated. There are lots of drivers, all having special dependencies.
So, perhaps the Buildroot packaging can be improved (it would be
nice!), but it will remain anyway a complex package.
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2018-08-23 11:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-23 9:08 [Buildroot] [PATCH] package/mesa3d: vulkan with x11 needs dri3 Yann E. MORIN
2018-08-23 10:11 ` Thomas Petazzoni
2018-08-23 10:20 ` Yann E. MORIN
2018-08-23 11:23 ` Thomas Petazzoni [this message]
2018-08-23 14:36 ` Yann E. MORIN
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=20180823132357.1dd3a730@windsurf \
--to=thomas.petazzoni@bootlin.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