All of lore.kernel.org
 help / color / mirror / Atom feed
From: "thilo.cestonaro@ts.fujitsu.com" <thilo.cestonaro@ts.fujitsu.com>
To: "openembedded-core@lists.openembedded.org"
	<openembedded-core@lists.openembedded.org>
Subject: meta-toolchain and meta-toolchain-qt for specific image
Date: Wed, 19 Oct 2016 08:19:00 +0000	[thread overview]
Message-ID: <1476865139.6425.0.camel@ts.fujitsu.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 836 bytes --]

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
----------

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

[-- Attachment #2: smime.p7s --]
[-- Type: application/x-pkcs7-signature, Size: 3847 bytes --]

             reply	other threads:[~2016-10-19  8:19 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-19  8:19 thilo.cestonaro [this message]
     [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

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=1476865139.6425.0.camel@ts.fujitsu.com \
    --to=thilo.cestonaro@ts.fujitsu.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 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.