From: Jonathan Liu <net147@gmail.com>
To: Otavio Salvador <otavio.salvador@ossystems.com.br>
Cc: Paul Eggleton <paul.eggleton@linux.intel.com>,
Otavio Salvador <otavio@ossystems.com.br>,
yocto <yocto@yoctoproject.org>
Subject: Re: [meta-raspberrypi][PATCH v2] qtbase: enable Raspberry Pi support
Date: Mon, 26 Oct 2015 22:31:47 +1100 [thread overview]
Message-ID: <562E0F23.1040404@gmail.com> (raw)
In-Reply-To: <CAP9ODKqqQVBUX9vc3ysrXQMAfZxNFqcws5Tg7qrVJcAA7eHx5w@mail.gmail.com>
On 26/10/2015 10:28 PM, Otavio Salvador wrote:
> On Mon, Oct 26, 2015 at 6:24 AM, Jonathan Liu <net147@gmail.com> wrote:
>> On 26/10/2015 7:08 PM, Paul Eggleton wrote:
>> It would rebuild qtbase (and recipes depending on it) without Raspberry Pi
>> support for other machines.
>> I see similar machine-specific do_configure_prepend elsewhere (e.g.
>> https://github.com/Freescale/meta-fsl-arm/blob/master/qt5-layer/recipes-qt/qt5/qtbase_%25.bbappend).
>>
>> Otavio, any thoughts on a better way to handle this?
> We handle this moving it to a SoC subarch and using a dynamic package
> arch handler to put every package depending on it as a subarch as
> well. Ideally we could split the QPA module and build it separated. No
> clue if it is possible or not.
>
So for meta-fsl-arm, would only the qtbase-plugins package be using
machine-specific arch and the other qtbase packages be using
non-machine-specific arch?
Or is it done on a per-recipe rather than per-package granularity?
Regards,
Jonathan
next prev parent reply other threads:[~2015-10-26 11:32 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-25 22:43 [meta-raspberrypi][PATCH v2] qtbase: enable Raspberry Pi support Jonathan Liu
2015-10-26 8:08 ` Paul Eggleton
2015-10-26 8:24 ` Jonathan Liu
2015-10-26 11:28 ` Otavio Salvador
2015-10-26 11:31 ` Jonathan Liu [this message]
2015-10-26 12:09 ` Otavio Salvador
2015-10-26 9:15 ` Andrei Gherzan
2015-10-26 9:41 ` Paul Eggleton
2015-10-26 10:48 ` Jonathan Liu
2015-10-26 10:54 ` Paul Eggleton
2015-10-26 11:10 ` Jonathan Liu
2015-10-26 11:45 ` 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=562E0F23.1040404@gmail.com \
--to=net147@gmail.com \
--cc=otavio.salvador@ossystems.com.br \
--cc=otavio@ossystems.com.br \
--cc=paul.eggleton@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.