From: Martin Jansa <martin.jansa@gmail.com>
To: Paul Eggleton <paul.eggleton@linux.intel.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] gtk+: Add PACKAGECONFIG for directfb
Date: Mon, 16 Dec 2013 14:52:09 +0100 [thread overview]
Message-ID: <20131216135209.GD3706@jama> (raw)
In-Reply-To: <3470792.PBUdbl2oFv@helios>
[-- Attachment #1: Type: text/plain, Size: 2531 bytes --]
On Mon, Dec 16, 2013 at 01:23:56PM +0000, Paul Eggleton wrote:
> Hi Martin,
>
> On Monday 16 December 2013 14:15:25 Martin Jansa wrote:
> > * building without x11 doesn't work, because it sets default
> > gdkbackend to x11 and then requires cairo-xlib to be available
> > * checking for CAIRO_BACKEND... no
> > configure: error: Package requirements (cairo-xlib >= 1.6) were not met:
> >
> > No package 'cairo-xlib' found
> >
> > Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
> > ---
> > meta/recipes-gnome/gtk+/gtk+.inc | 6 +++++-
> > 1 file changed, 5 insertions(+), 1 deletion(-)
> >
> > diff --git a/meta/recipes-gnome/gtk+/gtk+.inc
> > b/meta/recipes-gnome/gtk+/gtk+.inc index 73d624c..5bf0bfe 100644
> > --- a/meta/recipes-gnome/gtk+/gtk+.inc
> > +++ b/meta/recipes-gnome/gtk+/gtk+.inc
> > @@ -14,9 +14,13 @@ X11DEPENDS = "virtual/libx11 libxext libxcursor libxrandr
> > libxdamage libxrender DEPENDS = "glib-2.0 pango atk jpeg libpng
> > gdk-pixbuf-native docbook-utils-native \ cairo gdk-pixbuf"
> >
> > -PACKAGECONFIG ??= "${@base_contains('DISTRO_FEATURES', 'x11', 'x11', '',
> > d)}" +PACKAGECONFIG ??= "${@base_contains('DISTRO_FEATURES', 'x11', 'x11',
> > '', d)} \ + ${@base_contains('DISTRO_FEATURES', 'directfb',
> > 'directfb', '', d)} \ +"
> >
> > PACKAGECONFIG[x11] = "--with-x=yes
> > --with-gdktarget=x11,--with-x=no,${X11DEPENDS}" +# without
> > --with-gdktarget=directfb it will check for cairo-xlib which isn't
> > available without X11 DISTRO_FEATURE +PACKAGECONFIG[directfb] =
> > "--with-gdktarget=directfb,,directfb"
> >
> > inherit autotools gtk-doc pkgconfig update-alternatives gtk-immodules-cache
>
> I was under the impression that directfb support was removed from GTK+ some
> time ago - is that not the case?
Hi,
I must admit that my real motivation is to really disable x11/xlib in
gtk+, not to use it with directfb backend (In order to resolve
unsatisfied dependency mdbus2 -> vala -> gtk+ in distro without x11
DISTRO_FEATURE). After enabling directfb PACKAGECONFIG in gtk+ _AND_
cairo it builds fine.
I've tested this with dora (gtk+-2.24.20) and master (gtk+-2.24.22)
and both have in configure.ac:
cairo_backend=$gdktarget
AC_ARG_WITH(gdktarget, [ --with-gdktarget=[[x11/win32/quartz/directfb]]
select non-default GDK target],
gdktarget=$with_gdktarget)
if test "x$cairo_backend" = "xx11"; then
cairo_backend=xlib
fi
--
Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 205 bytes --]
next prev parent reply other threads:[~2013-12-16 13:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-16 13:15 [PATCH] gtk+: Add PACKAGECONFIG for directfb Martin Jansa
2013-12-16 13:23 ` Paul Eggleton
2013-12-16 13:50 ` Burton, Ross
2013-12-16 13:52 ` Martin Jansa [this message]
2013-12-16 13:52 ` Burton, Ross
2014-07-02 12:35 ` Martin Jansa
2014-07-02 12:36 ` [PATCHv2] " Martin Jansa
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=20131216135209.GD3706@jama \
--to=martin.jansa@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=paul.eggleton@linux.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 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.