Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 2/2] mesa-common: install internal GL headers to libgl-dev
Date: Sun, 16 Oct 2011 09:52:17 +0100	[thread overview]
Message-ID: <1318755146.2342.80.camel@ted> (raw)
In-Reply-To: <1318688875.3158.5.camel@lenovo.internal.reciva.com>

On Sat, 2011-10-15 at 15:27 +0100, Phil Blundell wrote:
> On Sat, 2011-10-15 at 11:54 +0200, Martin Jansa wrote:
> >  FILES_${PN}-dbg += "${libdir}/dri/.debug/*"
> >  FILES_libegl-dbg += "${libdir}/egl/.debug/*"
> > +
> > +do_install_append () {
> > +    install -d ${D}/${includedir}/GL
> > +    cp -pPr ${S}/include/GL/internal* ${D}/${includedir}/GL
> > +}
> 
> Why is this needed?  If the internal headers are meant to be installed,
> why doesn't "make install" do that?  Or, conversely, if they aren't
> intended to be installed, why do we want them there?
> 
> Please add some commentary to the checkin message explaining the
> rationale for the patch.

Ideally we should write a patch fixing the Makefile so dri-swrast
installs the pieces the xserver needs to build. Does it need both
sarea.h and dri_interface.h or just the latter?

FWIW the dri-i9* drivers install the dri header but not sarea.h.

Cheers,

Richard




      reply	other threads:[~2011-10-16  8:58 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-15  9:54 [PATCH 1/2] mesa: package gl/egl/osmesa to separate packages Martin Jansa
2011-10-15  9:54 ` [PATCH 2/2] mesa-common: install internal GL headers to libgl-dev Martin Jansa
2011-10-15 10:28   ` Koen Kooi
2011-10-15 14:27   ` Phil Blundell
2011-10-16  8:52     ` Richard Purdie [this message]

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=1318755146.2342.80.camel@ted \
    --to=richard.purdie@linuxfoundation.org \
    --cc=openembedded-core@lists.openembedded.org \
    /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