From: Denys Dmytriyenko <denis@denix.org>
To: Khem Raj <raj.khem@gmail.com>
Cc: "openembedded-core@lists.openembedded.org"
<openembedded-core@lists.openembedded.org>
Subject: Re: meta-toolchain and meta-toolchain-qt for specific image
Date: Thu, 20 Oct 2016 09:24:40 -0400 [thread overview]
Message-ID: <20161020132440.GW2494@denix.org> (raw)
In-Reply-To: <432953B0-59CB-4E94-A670-C4BD4A12C88A@gmail.com>
On Wed, Oct 19, 2016 at 08:00:12PM -0700, Khem Raj wrote:
>
> > On Oct 19, 2016, at 1:19 AM, thilo.cestonaro@ts.fujitsu.com wrote:
> >
> > Hey!
> >
> > I want to create such a nice toolchain installation package for my image recipe.
> > The problem I currently hit is, that I need to do populate_sdk and populate_sdk_qt5 to have qt5 toolchain too.
> >
> > Now I had an idea to create a recipe for the SDK like:
> >
> > ----------
> > SUMMARY = "Meta package for building an installable toolchain"
> > LICENSE = "MIT"
> >
> > PR = "r0"
> >
> > inherit populate_sdk populate_sdk_qt5
> > —————
>
>
> what is the advantage of such a recipe?
I guess the question is more generic...
The advantages of a separate meta-toolchain* recipe:
* a lot of flexibility
* not tied to a specific image
* can carry a lot of SDK customizations
> > But how can I tell the recipe to additionally install all the "*-dev" packages which my original image recipe installs.
> > When I require the image recipe, the toolchain recipe does a do_rootfs task (which is not needed, as it is done by building the image).
> >
> > I read something about TOOLCHAIN_TARGET_TASK and adding all the "*-dev" packages I want to this. But that doesn't work.
> >
> > Any hints?
> >
> > cheers,
> > Thilo--
> > _______________________________________________
> > 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
next prev parent reply other threads:[~2016-10-20 13:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <58072ca7.c70f420a.fed0f.74b1SMTPIN_ADDED_BROKEN@mx.google.com>
2016-10-20 3:00 ` meta-toolchain and meta-toolchain-qt for specific image Khem Raj
2016-10-20 6:24 ` thilo.cestonaro
2016-10-24 4:36 ` Anders Darander
2016-10-25 7:28 ` thilo.cestonaro
2016-10-25 7:49 ` Anders Darander
2016-10-25 11:03 ` thilo.cestonaro
2016-10-20 13:24 ` Denys Dmytriyenko [this message]
2016-10-19 8:19 thilo.cestonaro
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=20161020132440.GW2494@denix.org \
--to=denis@denix.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=raj.khem@gmail.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.