All of lore.kernel.org
 help / color / mirror / Atom feed
From: "thilo.cestonaro@ts.fujitsu.com" <thilo.cestonaro@ts.fujitsu.com>
To: "anders@chargestorm.se" <anders@chargestorm.se>
Cc: "openembedded-core@lists.openembedded.org"
	<openembedded-core@lists.openembedded.org>
Subject: Re: meta-toolchain and meta-toolchain-qt for specific image
Date: Tue, 25 Oct 2016 07:28:27 +0000	[thread overview]
Message-ID: <1477380507.4894.4.camel@ts.fujitsu.com> (raw)
In-Reply-To: <20161024043614.3gqmsqpu2h52tnpr@ad.chargestorm.se>

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

Hey

> Well, have your image `inherit populate_sdk_qt5`, and then call
> 
> `bitbake <your-image> -c populate_sdk`. That'll give you the standard,
> image-based SDK, with Qt5 in it.
> 
Can the image and the sdk be build seperatly then? Or will a "bitbake <my-image>" build the qt5 toolchain directly too?
This is what I intended to get rid off. To be able to build the image and the sdk in two independed build steps.

Cheers,
Thilo

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

  reply	other threads:[~2016-10-25  7:28 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 [this message]
2016-10-25  7:49         ` Anders Darander
2016-10-25 11:03           ` thilo.cestonaro
2016-10-20 13:24   ` Denys Dmytriyenko
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=1477380507.4894.4.camel@ts.fujitsu.com \
    --to=thilo.cestonaro@ts.fujitsu.com \
    --cc=anders@chargestorm.se \
    --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.