From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2 2/3] package/mesa3d-headers: fix install of dri.pc
Date: Sat, 25 Apr 2020 22:58:23 +0200 [thread overview]
Message-ID: <20200425225823.2f68e8ef@windsurf.home> (raw)
In-Reply-To: <20191023062220.5646-2-bernd.kuhls@t-online.de>
Hello Bernd,
On Wed, 23 Oct 2019 08:22:19 +0200
Bernd Kuhls <bernd.kuhls@t-online.de> wrote:
> Due to the switch of mesa3d to the meson build system the upstream
> tarball does not include dri.pc.in anymore, it is created during the
> build now:
> https://cgit.freedesktop.org/mesa/mesa/tree/src/mesa/drivers/dri/meson.build?h=19.2#n93
>
> In order to provide dri.pc we need to add a version taken from a dri-
> based mesa3d build to our source repository, by doing so we can reduce
> the number of sed commands.
I am sorry, but I don't understand the reasoning behind this patch. If
the new meson build system produces a dri.pc file, why don't we use it?
What is wrong with it?
Thanks,
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2020-04-25 20:58 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-23 6:22 [Buildroot] [PATCH 1/3] package/x11r7/xserver_xorg-server: fix optional glx dependency Bernd Kuhls
2019-10-23 6:22 ` [Buildroot] [PATCH v2 2/3] package/mesa3d-headers: fix install of dri.pc Bernd Kuhls
2020-02-18 13:44 ` Vincent Fazio
2020-04-25 20:58 ` Thomas Petazzoni [this message]
2020-04-25 21:15 ` Bernd Kuhls
2020-04-25 21:26 ` Yann E. MORIN
2020-04-26 9:21 ` Yann E. MORIN
2020-05-08 14:42 ` Peter Korsgaard
2019-10-23 6:22 ` [Buildroot] [PATCH 3/3] package/x11r7/xserver_xorg-server: switch to virtual opengl provider Bernd Kuhls
2019-10-25 18:10 ` Thomas Petazzoni
2019-10-25 20:26 ` Bernd Kuhls
2019-10-25 18:10 ` [Buildroot] [PATCH 1/3] package/x11r7/xserver_xorg-server: fix optional glx dependency Thomas Petazzoni
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=20200425225823.2f68e8ef@windsurf.home \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.