[Buildroot] [PATCH v2 1/3] qt5: bump version to 5.5.0

[Julien CORJON]

Dear Thomas,

Le 19/07/2015 23:22, Thomas Petazzoni a écrit :
> Dear Julien Corjon,
>
> On Wed,  8 Jul 2015 20:35:53 +0200, Julien Corjon wrote:
>> QT5BASE_EGLFS_PLATFORM_HOOKS_SOURCES is no longer useful since eglfs does not
>> depend on the device makespecs anymore. Instead, backends are autodetected by
>> configure [1].
>>
>> 0008-forkd-disable-eventfd-for-uclibc.patch disable missing eventfd in new Qt
>> 3rd party forkd for uClibc toolchains.
>>
>> Remove patches commited in Qt mainline and update pending one
>>
>> [1] https://codereview.qt-project.org/#/c/107548/
>>
>> Tested-by: Julien Corjon <corjon.j at ecagroup.com> Full compilation on ARM/uClibc
>> Tested-by: Julien Corjon <corjon.j at ecagroup.com> Partialy compiled and tested
>>    on i.MX6/linaro with OpenGL backend
>>
>> Signed-off-by: Julien Corjon <corjon.j at ecagroup.com>
>
> I was about to apply this, but unfortunately, it breaks the build with
> rpi-userland as the egl provider:
>
> /home/test/outputs/qt5/host/usr/arm-buildroot-linux-uclibcgnueabi/sysroot/usr/include/interface/vcos/vcos_types.h:38:33: fatal error: vcos_platform_types.h: No such file or directory
>   #include "vcos_platform_types.h"
>

This topic looks reccurent with rpi-userland on buildroot (for example [1])

This is because somes headers are in interface/vcos/pthread/ instead of 
interface/vcos

This proble is solved in qt with linux-rasp-pi-g++ device qmake 
configuration[2] but buildroot use a specific device to ease the 
toolchain integration.

I'm not sure how to handle this issue. Should I make a specific hook for 
rasp-pi (and maybe rasp-pi2) or should i try to replace buildroot 
specific device with real ones?

> I checked, and without your patches, the build works fine. The
> defconfig I'm testing is:
>
> BR2_arm=y
> BR2_TOOLCHAIN_EXTERNAL=y
> BR2_TOOLCHAIN_EXTERNAL_CUSTOM=y
> BR2_TOOLCHAIN_EXTERNAL_DOWNLOAD=y
> BR2_TOOLCHAIN_EXTERNAL_URL="http://autobuild.buildroot.org/toolchains/tarballs/br-arm-full-2015.05-496-g85945aa.tar.bz2"
> BR2_TOOLCHAIN_EXTERNAL_HEADERS_4_1=y
> BR2_TOOLCHAIN_EXTERNAL_LOCALE=y
> # BR2_TOOLCHAIN_EXTERNAL_HAS_THREADS_DEBUG is not set
> BR2_TOOLCHAIN_EXTERNAL_INET_RPC=y
> BR2_TOOLCHAIN_EXTERNAL_CXX=y
> BR2_PACKAGE_QT5=y
> BR2_PACKAGE_QT5BASE_LICENSE_APPROVED=y
> BR2_PACKAGE_QT5BASE_EGLFS=y
> BR2_PACKAGE_QT5BASE_JPEG=y
> BR2_PACKAGE_QT5BASE_PNG=y
> BR2_PACKAGE_QT5DECLARATIVE=y
> BR2_PACKAGE_QT5MULTIMEDIA=y
> BR2_PACKAGE_QT5QUICK1=y
> BR2_PACKAGE_QT5SENSORS=y
> BR2_PACKAGE_QT5SERIALPORT=y
> BR2_PACKAGE_QT5SVG=y
> BR2_PACKAGE_QJSON=y
> BR2_PACKAGE_QUAZIP=y
> BR2_PACKAGE_RPI_USERLAND=y
>
> Maybe Bernd or Yann can help with this Raspberry Pi specific issue?

Bernd, Yann, any advice?

>
> It's clearly a header path missing. It's probably caused by the
> refactoring of how the platform-specific EGL stuff is handled in Qt5.
>
> Thomas
>

Regards,

Julien

[1] http://lists.busybox.net/pipermail/buildroot/2013-March/068101.html
[2] 
http://code.qt.io/cgit/qt/qtbase.git/tree/mkspecs/devices/linux-rasp-pi-g++/qmake.conf