Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Samuli Piippo <samuli.piippo@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [meta-qt5][PATCH 06/11] qt5: make qt5.inc reusable qt5-module.bbclass
Date: Wed, 14 Oct 2015 15:50:14 +0300	[thread overview]
Message-ID: <561E4F86.10007@gmail.com> (raw)
In-Reply-To: <55DC1737.1070201@theqtcompany.com>

On 25.08.2015 10:20, Samuli Piippo wrote:
> On 24.08.2015 15:45, Martin Jansa wrote:
>> On Mon, Aug 24, 2015 at 12:13:52PM +0300, Samuli Piippo wrote:
>>> qt5.inc has common parts that can be used to build any Qt5 module.
>>> Make it a bbclass so that it is easily usable from other meta layers.
>>
>> require recipes-qt/qt5/qt5.inc
>>
>> can be used in other layers as well
>>
>
> It can, but as a bblclass it would make it clear that it's a supported
> thing to do, like qmake5 currently is.
> And maybe help guide further changes so that it remains usable from
> other layers as well.
>

Is this something that you can consider adding in?
I'll do a rebase for it, if it is.

-samuli


  parent reply	other threads:[~2015-10-14 12:49 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-24  9:13 [meta-qt5][PATCH 00/11] upstreaming Qt for Device Creation changes Samuli Piippo
2015-08-24  9:13 ` [meta-qt5][PATCH 01/11] qt5: make populate_sdk_qt5 reusable Samuli Piippo
2015-08-24  9:13 ` [meta-qt5][PATCH 02/11] qt5: improve Qt module package handling Samuli Piippo
2015-08-24  9:13 ` [meta-qt5][PATCH 03/11] qt5: improve support for native and nativesdk modules Samuli Piippo
2015-08-24  9:13 ` [meta-qt5][PATCH 04/11] qt5: add host paths to qt.conf Samuli Piippo
2015-08-24  9:13 ` [meta-qt5][PATCH 05/11] qt5: disable debian auto renaming Samuli Piippo
2015-08-24  9:13 ` [meta-qt5][PATCH 06/11] qt5: make qt5.inc reusable qt5-module.bbclass Samuli Piippo
2015-08-24 12:45   ` Martin Jansa
2015-08-25  7:20     ` Samuli Piippo
2015-10-14 12:47       ` Samuli Piippo
2015-10-14 12:50       ` Samuli Piippo [this message]
2015-08-24  9:13 ` [meta-qt5][PATCH 07/11] qttools: use one recipe for all compilations Samuli Piippo
2015-08-24 12:46   ` Martin Jansa
2015-08-24  9:13 ` [meta-qt5][PATCH 08/11] qtbase: remove dependency to sqlite Samuli Piippo
2015-08-24  9:13 ` [meta-qt5][PATCH 09/11] qtbase: PACKAGECONFIGs for libproxy and libinput Samuli Piippo
2015-08-24  9:13 ` [meta-qt5][PATCH 10/11] qtlocation: use correct dependencies Samuli Piippo
2015-08-24  9:13 ` [meta-qt5][PATCH 11/11] qtwebengine: fix problem with recursive qmake call Samuli Piippo
2015-08-24 12:42 ` [meta-qt5][PATCH 00/11] upstreaming Qt for Device Creation changes Martin Jansa

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=561E4F86.10007@gmail.com \
    --to=samuli.piippo@gmail.com \
    --cc=openembedded-devel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox