[meta-freescale] (off topic) exporting a SDK with Qt5

Otavio Salvador otavio at ossystems.com.br
Mon Oct 20 19:14:18 PDT 2014


Hello Alfonso,

On Sat, Oct 4, 2014 at 4:24 PM, Otavio Salvador <otavio at ossystems.com.br> wrote:
> On Fri, Oct 3, 2014 at 8:53 PM, Alfonso Tamés <alfonso at tames.com> wrote:
>> I just bitbaked a fsl-image-multimedia-full with qt5 and a
>> meta-toolchain-qt5 using master branch.
>>
>> When I run qmake -v this is the output:
>>
>> alfonso at mufilinux:~$
>> /opt/poky/1.7/sysroots/x86_64-pokysdk-linux/usr/bin/qt5/qmake -v
>> QMake version 3.0
>> Using Qt version 5.3.1 in
>> /opt/yocto/master_egl/build/tmp/sysroots/x86_64-linux/opt/poky/1.7/sysroots/x86_64-pokysdk-linux/usr/lib
>>
>>
>> And this is the output from qmake generated from Daisy:
>>
>> alfonso at mufilinux:~$
>> /opt/poky/1.6.1/sysroots/x86_64-pokysdk-linux/usr/bin/qt5/qmake -v
>> QMake version 3.0
>> Using Qt version 5.2.1 in
>> /opt/poky/1.6.1/sysroots/cortexa9hf-vfp-neon-poky-linux-gnueabi/usr/lib
>>
>>
>> As you can see the qmake from master branch is pointing to a non existing
>> directory on the wrong sysroot.
>
> It does; I am working on a toolchain issue for PPC and a packagedata
> issue (which broke mx53 for example) and once I solve these two issues
> which are affecting our customers I will try to look at this.
>
> Thanks for the testing case; this speeds my testing.

I think I narrowed this down. It was a mix of things and it seems to
work fine now.

Be sure to include the patches in meta-qt5 which I sent today :)

-- 
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


More information about the meta-freescale mailing list