Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] package/mesa3d-headers: fix install of dri.pc
Date: Tue, 22 Oct 2019 23:02:39 +0200	[thread overview]
Message-ID: <20191022230239.5de5d75b@windsurf> (raw)
In-Reply-To: <20191012173011.11419-1-bernd.kuhls@t-online.de>

On Sat, 12 Oct 2019 19:30:11 +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.
> 
> Signed-off-by: Bernd Kuhls <bernd.kuhls@t-online.de>

But does it make sense for mesa3d-headers to install dri.pc in the
first place ? mesa3d-headers is normally only supposed to install the
Khronos headers that some OpenGL implementation do not provide.

I'm not sure it makes sense for it to install dri.pc.

Could you give more details about the situation you've encountered
where dri.pc was missing, and that let you to propose this patch ? This
might help figuring out what is the right solution (which may turn out
to be your proposal, but I'd like to understand better).

Thanks!

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

  reply	other threads:[~2019-10-22 21:02 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-12 17:30 [Buildroot] [PATCH 1/1] package/mesa3d-headers: fix install of dri.pc Bernd Kuhls
2019-10-22 21:02 ` Thomas Petazzoni [this message]
2019-10-23  6:25   ` Bernd Kuhls

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=20191022230239.5de5d75b@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