From: Denys Dmytriyenko <denis@denix.org>
To: Ross Burton <ross.burton@intel.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 2/2] mesa: add PACKAGECONFIG for gbm
Date: Mon, 02 May 2016 22:54:09 -0400 [thread overview]
Message-ID: <20160503025409.GC27602@denix.org> (raw)
In-Reply-To: <20160426144925.GG31113@denix.org>
On Tue, Apr 26, 2016 at 10:49:25AM -0400, Denys Dmytriyenko wrote:
> On Tue, Apr 26, 2016 at 02:58:23PM +0100, Ross Burton wrote:
> > gbm is an optional library and some environments (for example, mesa-gl where
> > there are separate drivers that provide libgbm) may not want to build it.
> >
> > Signed-off-by: Ross Burton <ross.burton@intel.com>
>
> I was now able to build mesa-gl with TI SGX GLES and own libgbm. Thanks!
>
> Acked-by: Denys Dmytriyenko <denys@ti.com>
Ross,
I would like to see these 2 patches pushed early, even if virtual/libgbm
rework isn't ready yet. Thanks.
--
Denys
> > ---
> > meta/recipes-graphics/mesa/mesa.inc | 6 ++++--
> > 1 file changed, 4 insertions(+), 2 deletions(-)
> >
> > diff --git a/meta/recipes-graphics/mesa/mesa.inc b/meta/recipes-graphics/mesa/mesa.inc
> > index 442479a..a4e5351 100644
> > --- a/meta/recipes-graphics/mesa/mesa.inc
> > +++ b/meta/recipes-graphics/mesa/mesa.inc
> > @@ -24,11 +24,13 @@ REQUIRED_DISTRO_FEATURES = "opengl"
> >
> > EXTRA_OECONF = "--enable-shared-glapi"
> >
> > -PACKAGECONFIG ??= "egl gles dri ${MESA_CRYPTO} \
> > +PACKAGECONFIG ??= "gbm egl gles dri ${MESA_CRYPTO} \
> > ${@bb.utils.contains('DISTRO_FEATURES', 'x11', 'x11', '', d)}\
> > ${@bb.utils.contains('DISTRO_FEATURES', 'wayland', 'wayland', '', d)}\
> > "
> >
> > +PACKAGECONFIG[gbm] = "--enable-gbm,--disable-gbm"
> > +
> > X11_DEPS = "xf86driproto glproto virtual/libx11 libxext libxxf86vm libxdamage libxfixes"
> > PACKAGECONFIG[x11] = "--enable-glx-tls,--disable-glx,${X11_DEPS}"
> > PACKAGECONFIG[xvmc] = "--enable-xvmc,--disable-xvmc,libxvmc"
> > @@ -37,7 +39,7 @@ PACKAGECONFIG[wayland] = ",,wayland-native wayland"
> > DRIDRIVERS = "swrast"
> > DRIDRIVERS_append_x86 = ",radeon,r200,nouveau,i965,i915"
> > DRIDRIVERS_append_x86-64 = ",radeon,r200,nouveau,i965,i915"
> > -PACKAGECONFIG[dri] = "--enable-dri --with-dri-drivers=${DRIDRIVERS} --enable-gbm, --disable-dri, dri2proto libdrm"
> > +PACKAGECONFIG[dri] = "--enable-dri --with-dri-drivers=${DRIDRIVERS}, --disable-dri, dri2proto libdrm"
> > PACKAGECONFIG[dri3] = "--enable-dri3, --disable-dri3, dri3proto presentproto libxshmfence"
> >
> > PACKAGECONFIG[gles] = "--enable-gles1 --enable-gles2, --disable-gles1 --disable-gles2"
> > --
> > 2.8.0.rc3
> >
> > --
> > _______________________________________________
> > Openembedded-core mailing list
> > Openembedded-core@lists.openembedded.org
> > http://lists.openembedded.org/mailman/listinfo/openembedded-core
> --
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core
prev parent reply other threads:[~2016-05-03 2:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-26 13:58 [PATCH 1/2] mesa-gl: add missing MESA_CRYPTO to PACKAGECONFIG Ross Burton
2016-04-26 13:58 ` [PATCH 2/2] mesa: add PACKAGECONFIG for gbm Ross Burton
2016-04-26 14:49 ` Denys Dmytriyenko
2016-05-03 2:54 ` Denys Dmytriyenko [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=20160503025409.GC27602@denix.org \
--to=denis@denix.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=ross.burton@intel.com \
/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