From: Pampolini Matteo <matteo.pampolini@selex-es.com>
To: Leonardo Sandoval <leonardo.sandoval.gonzalez@linux.intel.com>,
"yocto@yoctoproject.org" <yocto@yoctoproject.org>
Subject: Re: Which is the best strategy to customize Qt configuration?
Date: Mon, 13 Jul 2015 16:05:08 +0000 [thread overview]
Message-ID: <1436803507811.898@selex-es.com> (raw)
In-Reply-To: <22658_1436802429_55A3DD7C_22658_11739_1_55A3DDA1.8020100@linux.intel.com>
Many thanks Leonardo.
However I still have some doubts: as far as I understood I should remove the dependencies from glib and gstreamer inside DEPENDS variable as it appears in qt4.inc file, otherwise BitBake, correctly, downloads and compiles them to satisfy Qt requirements, am I right?
If so, how can I avoid this from within my layer?
Regards, Matteo
________________________________________
From: Leonardo Sandoval <leonardo.sandoval.gonzalez@linux.intel.com>
Sent: Monday, July 13, 2015 5:47 PM
To: Pampolini Matteo; yocto@yoctoproject.org
Subject: Re: [yocto] Which is the best strategy to customize Qt configuration?
On 07/13/2015 09:23 AM, Pampolini Matteo wrote:
> Hello everybody,
>
>
> my name is Matteo and I'm writing from Italy.
>
>
> 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">
>
> Now I'm in trouble a little bit because I do not exactly now which Qt-related files should be included in my layer and how they should relate with the provided ones, may you please help me?
>
Dependencies can be found using the '-g' bitbake command line. That
command produces .dot files, and you can parse these to figure out what
you want.
>
> Many thanks in advance for your kind support,
>
>
> Matteo
>
>
>
prev parent reply other threads:[~2015-07-13 16:05 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
[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 [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=1436803507811.898@selex-es.com \
--to=matteo.pampolini@selex-es.com \
--cc=leonardo.sandoval.gonzalez@linux.intel.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.