From: Andrei Gherzan <andrei@gherzan.ro>
To: Otavio Salvador <otavio.salvador@ossystems.com.br>
Cc: yocto@lists.yoctoproject.org, Otavio Salvador <otavio@ossystems.com.br>
Subject: Re: [meta-raspberrypi][PATCH] Revert "qtbase: Enable EGLFS support"
Date: Mon, 2 Oct 2017 15:35:17 +0100 [thread overview]
Message-ID: <20171002143517.GA11297@carbonA> (raw)
In-Reply-To: <CAP9ODKqV0ZbkY4GQJuwRxJ+n1gf7R9izcHV77fAby2fk4E48QQ@mail.gmail.com>
On Wed, Sep 27, 2017 at 02:45:07PM -0300, Otavio Salvador wrote:
> Hello Martin,
>
> On Wed, Sep 27, 2017 at 2:34 PM, Martin Jansa <martin.jansa@gmail.com> wrote:
> ...
> >> Martin, do you have any idea how other alternative we have?
> >
> > In theory you can set QT_PACKAGES_ARCH to MACHINE_ARCH in rpi-base.inc
> > to make it explicit, but that's also really bad (as e.g. rpi2 and rpi3
> > will each build it's own qtwebengine and all it's deps even when it
> > should be the same for both).
>
> Agreed and that was the reason of we create MACHINE_SOCARCH in
> meta-freescale. It allows for SoC specific packages but compatible
> across machines.
>
> --
> Otavio Salvador O.S. Systems
> http://www.ossystems.com.br http://code.ossystems.com.br
> Mobile: +55 (53) 9981-7854 Mobile: +1 (347) 903-9750
Merged to master in the meanwhile.
--
Andrei Gherzan
gpg: rsa4096/D4D94F67AD0E9640 | t: @agherzan
prev parent reply other threads:[~2017-10-02 14:36 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-27 15:23 [meta-raspberrypi][PATCH] Revert "qtbase: Enable EGLFS support" Martin Jansa
2017-09-27 17:13 ` Andrei Gherzan
2017-09-27 17:20 ` Khem Raj
2017-09-27 17:28 ` Otavio Salvador
2017-09-27 18:53 ` Manjukumar Harthikote Matha
2017-09-27 19:22 ` Otavio Salvador
2017-09-27 20:14 ` Manjukumar Harthikote Matha
2017-09-27 20:19 ` Otavio Salvador
2017-09-27 20:33 ` Trevor Woerner
2017-09-27 17:23 ` Otavio Salvador
2017-09-27 17:34 ` Martin Jansa
2017-09-27 17:45 ` Otavio Salvador
2017-10-02 14:35 ` Andrei Gherzan [this message]
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=20171002143517.GA11297@carbonA \
--to=andrei@gherzan.ro \
--cc=otavio.salvador@ossystems.com.br \
--cc=otavio@ossystems.com.br \
--cc=yocto@lists.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.