On 2 November 2016 at 22:10, Paul Eggleton
wrote:
> Only if they have "touchscreen" in IMAGE_FEATURES - do any of the machines
> we
> build for on the autobuilder do that?
>
I thought the qemu machines did, but I was wrong.
Thanks,
Ross
--
On Wed, 02 Nov 2016 11:08:49 Burton, Ross wrote:
> On 2 November 2016 at 03:01, Paul Eggleton
> wrote:
> > I have merged both of the patches to master and taken the liberty of
> > merging
> > them to morty as well, just so it isn't horribly broken. I appreciate it's
On 2 November 2016 at 03:01, Paul Eggleton
wrote:
> I have merged both of the patches to master and taken the liberty of
> merging
> them to morty as well, just so it isn't horribly broken. I appreciate it's
> still slightly broken from some perspectives.
>
> I
BTW, earlier there was a question about what the correct mailing list for
meta-qt4 is. According to the README it's yo...@yoctoproject.org. I've updated
the layer index page [1] accordingly (it didn't list any earlier).
Cheers,
Paul
[1]
I have merged both of the patches to master and taken the liberty of merging
them to morty as well, just so it isn't horribly broken. I appreciate it's
still slightly broken from some perspectives.
I suspect the reason this was done was to remove the tslib dependency by
default so that meta-oe
Having some more experience with it, my suggestion would be to REVERT
c4671873af5ab6c7d15ca397538f154c11c3486e "qt4-embedded.inc: provide
PACKAGECONFIG for tslib".
The problem with using MACHINE_FEATURES for building the qt4 libs is that the
qt4 package becomes machine-specific, and if
Hi
I sent a similar patch:
https://lists.yoctoproject.org/pipermail/yocto/2016-October/032661.html
Both fix the build error with the HEAD of meta-qt4.
Question is if "touchscreen" in MACHINE_FEATURES should build for
tslib by default.
If yes, your patch is needed.
However the error will pop up
When "touchscreen" is in the MACHINE_FEATURES, packagegroup-core-qt4e
will RDEPEND on qt4-embedded-plugin-mousedriver-tslib, but that
library is not being built by default, resulting in an error like:
opkg_prepare_url_for_install: Couldn't find anything to satisfy