| Summary: | qt5webengine should not use WEBENGINE_CONFIG | ||
|---|---|---|---|
| Product: | buildroot | Reporter: | JeffyCN <jeffy.chen> |
| Component: | Other | Assignee: | Peter Seiderer <ps.report> |
| Status: | RESOLVED MOVED | ||
| Severity: | normal | CC: | buildroot, yann.morin.1998 |
| Priority: | P5 | ||
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Host: | Target: | ||
| Build: | |||
|
Description
JeffyCN
2019-12-19 01:56:05 UTC
Thanks for the bug report and suggested patch (and sorry for the delayed response). Meanwhile Nathan Ford took care of the suggested patch plus missing webp mux and alsa support ([1], [2])..., the suggested patch seems to work for the Qt-latest/5.12.x case ([3])... One further question out of interest, on which hardware do you run qtwebengine and how (or which buildroot config/defconfig do you use)? There is a report from one buildroot user not to be able to run the minimal example on RaspberryPi Zero (see [4] and [5])... [1] http://lists.busybox.net/pipermail/buildroot/2020-January/272066.html [2] https://patchwork.ozlabs.org/patch/1227357/ [3] http://lists.busybox.net/pipermail/buildroot/2020-February/274385.html [4] http://lists.busybox.net/pipermail/buildroot/2020-February/273320.html [5] http://lists.busybox.net/pipermail/buildroot/2020-February/273329.html (In reply to Peter Seiderer from comment #1) Hi Peter, Thanks for noticing that. We are using a custom version of buildroot(2018.02-rc3 with qt5 bumpped to 5.12.2): https://github.com/rockchip-linux/buildroot/tree/rockchip/2018.02-rc3 Configs: rockchip_*_defconfig, running on a few arm/arm64 based platforms(rockchip evb boards) We've tested minimal too, did see some issues on arm 32bit platforms: 1/ 5.12.2 would report segfaults, should be fine for the newer versions(e.g. 5.12.5): https://github.com/rockchip-linux/buildroot/commit/6e4fc810cdea122b1bd86c8649d276c485f794f9 2/ I can't recall the exact phenomenon, could be the same as RaspberryPi's... It seems like the chromium might be compiled with different fpu setting than the other packages on arm 32bit platform, which is because it would try to detect neon support from the qt5base's CFLAGS and currently buildroot would not specify that there, but embedded in the gcc toolchain instead: qt5webengine-5.12.2$ vi src/core/config/linux.pri # TODO: use neon detection from qtbase !lessThan(MARMV, 8) { gn_args += arm_use_neon=true } else { MFPU = $$extractCFlag("-mfpu=.*") !isEmpty(MFPU):contains(MFPU, ".*neon.*") { gn_args += arm_use_neon=true } else { gn_args += arm_use_neon=false # If the toolchain does not explicitly specify to use NEON instructions # we use arm_neon_optional for ARMv7 equals(MARMV, 7): gn_args += arm_optionally_use_neon=true } } https://github.com/rockchip-linux/buildroot/commit/8e832026edbb6e70df283629dadca981854866ad Hi guys, the qt packages are using pkg-qmake.mk now, and the pending patch seems to be wrong..: $(QT5WEBENGINE_QMAKEFLAGS) -- $(QT5WEBENGINE_CONFIG)) needs a '--' between webengine config and other qmake flags. Thank you for your report.
The issue tracker for the Buildroot project has been moved to
the Gitlab.com issue tracker:
https://gitlab.com/buildroot.org/buildroot/-/issues
We are taking this opportunity to close old issues in this old
tracker. If you believe your issue is still relevant, please
open one in the new issue tracker.
Thank you!
|