From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: Pampolini Matteo <matteo.pampolini@selex-es.com>,
Leonardo Sandoval <leonardo.sandoval.gonzalez@linux.intel.com>
Cc: yocto@yoctoproject.org
Subject: Re: Which is the best strategy to customize Qt configuration?
Date: Mon, 13 Jul 2015 17:05:48 +0100 [thread overview]
Message-ID: <10339148.fJj1pddUcL@peggleto-mobl.ger.corp.intel.com> (raw)
In-Reply-To: <55A3DDA1.8020100@linux.intel.com>
On Monday 13 July 2015 10:47:45 Leonardo Sandoval wrote:
> On 07/13/2015 09:23 AM, Pampolini Matteo wrote:
> > I'm involved in a project that requires a very customized Linux
> > installation and I think Yocto is the best choice for this purpose.
> >
> > I was able to build and run some images from Poky 1.8 reference and now
> > I'm trying to create my own one, with a custom configuration of Qt for
> > X11.
> >
> > In particular I would like to remove Phonon support to avoid
> > GStreamer/GLib dependencies: the quickest (and bad) solution was to
> > modify meta/recipes-qt/qt4/qt4.inc file and it works, of course.
> >
> > But in order to follow Yocto guidelines and learn the right approach, I
> > would like to create a new layer and, with proper use of .bbappend files,
> > create my own Qt custom configuration.
>
> For this point, you can create a new layer and inside a new image file.
> This image will basically inherit the one you want, then you need to
> remove the specific recipe. A possible way to remove it is though
> IMAGE_INSTALL_remove = "<pkg to remove">
That doesn't really help with Qt configuration - you can't change any of that
at the image level.
The way to set this properly is to look at how qt4.inc is structured - note
that the -phonon / -no-phonon option for example is set through a variable
QT_PHONON. There are several different ways you could set this:
1) Use a bbappend on the qt4-x11-free recipe that sets
QT_PHONON = "-no-phonon"
2) Set it from your distro config (or some include file from there) using
QT_PHONON_pn-qt4-x11-free = "-no-phonon"
3) Since this variable specifically is being set in the .inc file with ?= and is
reasonably well namespaced (i.e. has a name which is unlikely to clash with
variables used in other recipes for a different purpose), you could
alternatively just set it from your distro config simply as
QT_PHONON = "-no-phonon"
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
next prev parent reply other threads:[~2015-07-13 16:07 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-13 14:23 Which is the best strategy to customize Qt configuration? Pampolini Matteo
2015-07-13 15:47 ` Leonardo Sandoval
2015-07-13 16:05 ` Paul Eggleton [this message]
[not found] ` <22658_1436803637_55A3E234_22658_12077_1_10339148.fJj1pddUcL@peggleto-mobl.ger.corp.intel.com>
2015-07-13 16:18 ` Pampolini Matteo
2015-07-13 16:38 ` Paul Eggleton
2015-07-13 18:04 ` Martin Jansa
2015-07-13 18:10 ` Elvis Dowson
2015-07-14 8:06 ` Paul Eggleton
[not found] ` <15988_1436861200_55A4C310_15988_12931_1_59871636.IPlF15pPhG@peggleto-mobl.ger.corp.intel.com>
2015-07-14 13:02 ` Pampolini Matteo
[not found] ` <22658_1436802429_55A3DD7C_22658_11739_1_55A3DDA1.8020100@linux.intel.com>
2015-07-13 16:05 ` Pampolini Matteo
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=10339148.fJj1pddUcL@peggleto-mobl.ger.corp.intel.com \
--to=paul.eggleton@linux.intel.com \
--cc=leonardo.sandoval.gonzalez@linux.intel.com \
--cc=matteo.pampolini@selex-es.com \
--cc=yocto@yoctoproject.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 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.