Skip to main content
VKare.1
VKare.1
Associate II
January 28, 2020
Solved

problems with qtwebkit

  • January 28, 2020
  • 1 reply
  • 1013 views

I'm trying to create new image with my app, that needs qtwebkitwidgets, but have some problems with that. When bitbake starting compile qtwebkit-my host pc freezes. I read that post https://community.st.com/s/question/0D50X0000AVSWK1SQP/what-is-the-process-for-initializing-the-openembedded-build-environment-stexampleimageqt about qtwebkit, but in my case it doesn't work. My MACHINE=stm32mp1 DISTRO=openstlinux-x11. I tried bitbake with -k and I tried to launch compilation again, first compile stoped at 38%, after rebooting my host-it's 0% and freeze.

Is any alternative ideas how I can install qtwebkit to use my app?

This topic has been closed for replies.
Best answer by Olivier GALLIEN

Hi @VKare.1​ 

Looks to work in this post

https://community.st.com/s/question/0D50X0000B7Ykl5SQC/getting-failure-while-compiling-qtwebkit-for-yocto

But with this conf :

DISTRO=openstlinux-eglfs MACHINE=stm32mp1-eval source layers/meta-st/scripts/envsetup.sh

bitbake st-example-image-qt

Can you make a try.

Else, what host system are you using ?

Does it fit minimal requirement for Yocto build ( cf https://wiki.st.com/stm32mpu/wiki/PC_prerequisites )

Hope it help

Olivier

1 reply

Olivier GALLIEN
Olivier GALLIENAnswer
Technical Moderator
February 5, 2020

Hi @VKare.1​ 

Looks to work in this post

https://community.st.com/s/question/0D50X0000B7Ykl5SQC/getting-failure-while-compiling-qtwebkit-for-yocto

But with this conf :

DISTRO=openstlinux-eglfs MACHINE=stm32mp1-eval source layers/meta-st/scripts/envsetup.sh

bitbake st-example-image-qt

Can you make a try.

Else, what host system are you using ?

Does it fit minimal requirement for Yocto build ( cf https://wiki.st.com/stm32mpu/wiki/PC_prerequisites )

Hope it help

Olivier

Olivier GALLIEN In order to give better visibility on the answered topics, please click on 'Accept as Solution' on the reply which solved your issue or answered your question.
Terms & ConditionsAccessibility statement