Building Custome Yocto Image for WP8548


#1

I want customize Yocto Image that supports QT(cute). How I can achieve this?


#2

Hello you can try to add layer meta-QT5 in Yocto and try to build the bsp.

After you need to build the cross tool chain to compile QT5 application.

I use QT5 with imx6 (base on Yocto 2.4) but mainly for HMI application.


#3

Thank you @Francis.duhaut
I will try.

After you need to build the cross tool chain to compile QT5 application.
I am also using QT5 with iMX 6, so I am using gcc-linaro cross toolchain for QT will it work with this?


#4

you can build the toolchain with yocto for QT :

bitbake meta-toolchain


#5

ok. I will try.

Thank you @Francis.duhaut


#6

I am getting this error.
I have added new meta-qt5 layer in OE directory & enable the layer in build.sh

hitesh@DND087:~/Downloads/yocto$ make image_bin
“meta-swi/build.sh” -p poky/ -o meta-openembedded/ -l meta-swi -x “kernel/.git” -j 9 -t 9 -M -a “MANGOH_WIFI_REPO=”/home/hitesh/Downloads/yocto/mangOH/WiFi"" -m swi-mdm9x15 -a KBRANCH_DEFAULT_MDM9X15=standard/swi-mdm9x15-yocto-wpx5xx -a KMETA_DEFAULT_MDM9X15=meta-yocto-1.7-ref -b build_bin -q
Poky dir: /home/hitesh/Downloads/yocto/poky
OE meta: /home/hitesh/Downloads/yocto/meta-openembedded
SWI meta dir: /home/hitesh/Downloads/yocto/meta-swi
Linux repo dir: /home/hitesh/Downloads/yocto/kernel/.git
Number of make threads 9
Number of bitbake tasks 9
With mangOH
Extra options added - MANGOH_WIFI_REPO=/home/hitesh/Downloads/yocto/mangOH/WiFi
SWI machine: swi-mdm9x15
Extra options added - KBRANCH_DEFAULT_MDM9X15=standard/swi-mdm9x15-yocto-wpx5xx
Extra options added - KMETA_DEFAULT_MDM9X15=meta-yocto-1.7-ref
Build dir: /home/hitesh/Downloads/yocto/build_bin
Enable Qualcomm Proprietary bin

Shell environment set up for builds.

You can now run 'bitbake ’

Common targets are:
core-image-minimal
core-image-sato
meta-toolchain
meta-ide-support

You can also run generated qemu images with a command like ‘runqemu qemux86’
Error: bash is not set as default provider for /bin/sh
build is not guaranteed to work, aborting
Makefile:250: recipe for target ‘image_bin’ failed
make: *** [image_bin] Error 1


#7

@Francis.duhaut

please can you provide proper steps to rebuild image with qt5. I have downloaded source code from here- https://source.sierrawireless.com/resources/airprime/software/wpx5xx/wpx5xx-firmware-latest-release-components/


#8

This post may be of some help.


#9

thank you @shib
Nothing is there related to my question.
I need proper guide to rebuild with qt5 and legato application support.


#10

It was related to the error in your previous post.

If that isn’t an issue anymore, what are you currently stuck on?


#11

I am currently stuck on this


#12

Did you install the correct tool chain ??
32 bits or 64 bits (depend of your Linux system).

The link is on the Sierra website (same page that you download the source code).


#13

I have downloaded 64 bit toolchain but I didn’t install yet. Do I need to install on my system?


#14

It sounds like you are using the wrong version of the qt5 layer.
Make sure the qt5 layer version is compatible with that version of yocto.


#15

thank you @shib
Please can you provide me correct version of qt5 meta.


#16

I haven’t done anything with qt5 in embedded linux, but from what I can see…
yocto 2.2 is called Morty.
So I went to the qt5 layer github to the Morty branch.


#17

I have downloaded from here -https://github.com/meta-qt5/meta-qt5

one thing I wanted to confirm that after I downloaded meta-qt5, I added following line in build.sh

Enable the meta-qt5 layer

enable_layer “meta-qt5” “$OE/meta-qt5”

and put meta-qt5 folder inside meta-openembedded


#18

Yes you need it. The tool chain will be installed in /opt/


#19

Thank you @Francis.duhaut
Finally my building stage is started but please can you tell me why do I need this toolchain ?
and one more doubt after completion of building, Do I need qt5 toolchain?
If I need then how to compile for qt5 toolchain with legato application compatibility.


#20

Toolchain is use to build legato.
Legato need to be build separately