Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: Martin Jansa <martin.jansa@gmail.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] qt4-x11-free: disable QGtkStyle
Date: Fri, 20 Sep 2013 15:55:41 +0100	[thread overview]
Message-ID: <4410837.umzcAyviZD@helios> (raw)
In-Reply-To: <20130920144205.GJ18414@jama>

On Friday 20 September 2013 16:42:05 Martin Jansa wrote:
> On Fri, Sep 20, 2013 at 03:27:32PM +0100, Paul Eggleton wrote:
> > On Friday 20 September 2013 15:58:26 Andreas Müller wrote:
> > > On Fri, Sep 20, 2013 at 3:01 PM, Paul Eggleton
> > > 
> > > <paul.eggleton@linux.intel.com> wrote:
> > > > This currently leads to a floating dependency on GTK+. Since most
> > > > users
> > > > in an embedded context won't need this, just disable it by default.
> > > > 
> > > > Fixes [YOCTO #5116].
> > > > 
> > > > Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com>
> > > > ---
> > > > 
> > > >  meta/recipes-qt/qt4/qt4-x11-free.inc | 2 +-
> > > >  1 file changed, 1 insertion(+), 1 deletion(-)
> > > > 
> > > > diff --git a/meta/recipes-qt/qt4/qt4-x11-free.inc
> > > > b/meta/recipes-qt/qt4/qt4-x11-free.inc index 4b29f55..369b3d5 100644
> > > > --- a/meta/recipes-qt/qt4/qt4-x11-free.inc
> > > > +++ b/meta/recipes-qt/qt4/qt4-x11-free.inc
> > > > @@ -12,7 +12,7 @@ INC_PR = "r50"
> > > > 
> > > >  QT_GLFLAGS ?= "${@base_contains('DISTRO_FEATURES', 'opengl',
> > > >  '-opengl',
> > > >  '-no-opengl', d)} " QT_GLFLAGS_qemux86 = "-opengl"
> > > >  QT_GLFLAGS_qemuppc = "-opengl"
> > > > 
> > > > -QT_X11_FLAGS ?= "-no-xinerama -no-xkb"
> > > > +QT_X11_FLAGS ?= "-no-xinerama -no-xkb -no-gtkstyle"
> > > > 
> > > >  QT_CONFIG_FLAGS += "${QT_X11_FLAGS}"
> > > >  QT_BASE_LIB  ?= "libqt"
> > > 
> > > How about PACKAGECONFIG for this?
> > 
> > Ultimately I decided against introducing PACKAGECONFIG just for this,
> > because the Qt recipes currently avoid it (PACKAGECONFIG cannot support a
> > number of the additional library options for Qt since they are tri-state;
> > not to mention that PACKAGECONFIG isn't just a drop-in for Qt because it
> > doesn't use autotools/cmake and therefore doesn't use
> > EXTRA_OECONF/EXTRA_OECMAKE). I figured that the few users who do want
> > QGTKStyle can just set QT_X11_FLAGS as desired.
> 
> FWIW: I'm using PACKAGECONFIG in meta-qt5, you're right that it cannot
> cover all 3 states for each option, but most common scenarios need to
> select only between 2 and automatically added DEPENDS/RDEPENDS is big
> plus.

On this wider issue, I have given some thought to how we could expand 
PACKAGECONFIG to support multi-state options, although I'm hesitant to make 
the already slightly opaque PACKAGECONFIG syntax any more complicated. 
Something to think about further for the next development cycle perhaps.
 
> To support PACKAGECONFIG without autotools/cmake inherit I just add
> generated EXTRA_OECONF to QT_CONFIG_FLAGS.

I didn't try it but Peter reported that this caused a failure when he tried 
this as a solution (presumably because there is junk in EXTRA_OECONF already 
that isn't suitable for passing to Qt4's configure). It ought to be able to 
work though.

Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre


  reply	other threads:[~2013-09-20 14:55 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-20 13:01 [PATCH] qt4-x11-free: disable QGtkStyle Paul Eggleton
     [not found] ` <CALbNGRTFYp0yJ+Y9yTX8npPQaHmaaZOzet5EEwjSpULDWy3QYA@mail.gmail.com>
2013-09-20 14:27   ` Paul Eggleton
2013-09-20 14:42     ` Martin Jansa
2013-09-20 14:55       ` Paul Eggleton [this message]
2013-09-20 22:36 ` Otavio Salvador

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=4410837.umzcAyviZD@helios \
    --to=paul.eggleton@linux.intel.com \
    --cc=martin.jansa@gmail.com \
    --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