[yocto] Image SDK Generation With QT5

[Kosta Zertsekel]

Hi Charles,

>> I've created an image for the Raspberry Pi 2 which includes Qt5 and
>> the WiringPi library and it runs great on the device. However, when
>> I run the command 'bitbake myQtImage -c populate_sdk' I get the
>> Pi sysroot with everything in it but I don't get the x86-64 qmake
>> I need to cross compile on my desktop. When I run meta-toolchain-qt5
>> I get the x86-64 qmake I want but the wiringPi library isn't included
>> in the Pi sysroot.  What do I need to do to generate an SDK that
>> includes both the wiringPi library in the Pi sysroot and the x86-64 qmake?

Please provide your git link for people to clone and review.

Thanks,
--- KostaZ

________________________________________
From: yocto-bounces at yoctoproject.org <yocto-bounces at yoctoproject.org> on behalf of Charles Werther <cwerther3 at gmail.com>
Sent: Sunday, January 31, 2016 4:40 PM
To: yocto at yoctoproject.org
Subject: [yocto] Image SDK Generation With QT5

All,

I've created an image for the Raspberry Pi 2 which includes Qt5 and the WiringPi library and it runs great on the device. However, when I run the command 'bitbake myQtImage -c populate_sdk' I get the Pi sysroot with everything in it but I don't get the x86-64 qmake I need to cross compile on my desktop. When I run meta-toolchain-qt5 I get the x86-64 qmake I want but the wiringPi library isn't included in the Pi sysroot.  What do I need to do to generate an SDK that includes both the wiringPi library in the Pi sysroot and the x86-64 qmake?

Thanks,
Charles
--
_______________________________________________
yocto mailing list
yocto at yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[E-Banner]<http://www.mrv.com/blog>


MRV Communications is a global supplier of packet and optical solutions that power the world’s largest networks. Our products combine innovative hardware with intelligent software to make networks smarter, faster and more efficient.


The contents of this message, together with any attachments, are intended only for the use of the person(s) to whom they are addressed and may contain confidential and/or privileged information. If you are not the intended recipient, immediately advise the sender, delete this message and any attachments and note that any distribution, or copying of this message, or any attachment, is prohibited.