Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2 1/3] qt5: bump version to 5.5.0
Date: Sun, 19 Jul 2015 23:22:02 +0200	[thread overview]
Message-ID: <20150719232202.67a5bc98@free-electrons.com> (raw)
In-Reply-To: <1436380555-13657-1-git-send-email-corjon.j@ecagroup.com>

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@ecagroup.com> Full compilation on ARM/uClibc
> Tested-by: Julien Corjon <corjon.j@ecagroup.com> Partialy compiled and tested
>   on i.MX6/linaro with OpenGL backend
> 
> Signed-off-by: Julien Corjon <corjon.j@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"

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?

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
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

  parent reply	other threads:[~2015-07-19 21:22 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-08 18:35 [Buildroot] [PATCH v2 1/3] qt5: bump version to 5.5.0 Julien Corjon
2015-07-08 18:35 ` [Buildroot] [PATCH v2 2/3] qt5base: reorder patches Julien Corjon
2015-07-08 18:35 ` [Buildroot] [PATCH v2 3/3] qt5quick1, qt5script, qt5webkit: tag as legacy compatibility Julien Corjon
2015-07-10 14:20   ` [Buildroot] [PATCH v3 1/5] qt5: bump version to 5.5.0 Julien Corjon
2015-07-10 14:20     ` [Buildroot] [PATCH v3 2/5] qt5base: reorder patches Julien Corjon
2015-07-10 14:20     ` [Buildroot] [PATCH v3 3/5] qt5quick1, qt5script, qt5webkit: tag as legacy compatibility Julien Corjon
2015-07-10 14:20     ` [Buildroot] [PATCH v3 4/5] qt5webengine: new package Julien Corjon
2015-07-19 13:02       ` Thomas Petazzoni
2015-07-20  9:17         ` Julien CORJON
2015-07-20  9:25           ` Thomas Petazzoni
2015-12-23  9:40             ` Gary Bisson
2015-12-23  9:49               ` Thomas Petazzoni
2015-12-23 10:15                 ` Julien CORJON
2015-12-23 14:21                   ` Gary Bisson
2015-12-23 15:04                     ` Julien CORJON
2015-07-10 14:20     ` [Buildroot] [PATCH v3 5/5] qt/qt5webchannel: " Julien Corjon
2015-07-21  8:51     ` [Buildroot] [PATCH v4 0/4] qt5 bump to 5.5.0 Julien Corjon
2015-07-21  8:51       ` [Buildroot] [PATCH v4 1/4] qt5: bump version " Julien Corjon
2015-07-21  9:13         ` Thomas Petazzoni
2015-07-21  8:51       ` [Buildroot] [PATCH v4 2/4] qt/qt5base: reorder patches Julien Corjon
2015-07-21  8:51       ` [Buildroot] [PATCH v4 3/4] qt/qt5quick1, qt/qt5script, qt/qt5webkit: tag as legacy compatibility Julien Corjon
2015-07-21  8:51       ` [Buildroot] [PATCH v4 4/4] qt/qt5webchannel: new package Julien Corjon
2015-07-21 11:30       ` [Buildroot] [PATCH v5 0/4] qt5 bump to 5.5.0 Julien Corjon
2015-07-21 11:30         ` [Buildroot] [PATCH v5 1/4] qt5: bump version " Julien Corjon
2015-07-21 11:30         ` [Buildroot] [PATCH v5 2/4] qt/qt5base: reorder patches Julien Corjon
2015-07-21 11:30         ` [Buildroot] [PATCH v5 3/4] qt/qt5quick1, qt/qt5script, qt/qt5webkit: tag as legacy compatibility Julien Corjon
2015-07-21 11:30         ` [Buildroot] [PATCH v5 4/4] qt/qt5webchannel: new package Julien Corjon
2015-07-21 21:41         ` [Buildroot] [PATCH v5 0/4] qt5 bump to 5.5.0 Thomas Petazzoni
2015-07-19 21:22 ` Thomas Petazzoni [this message]
2015-07-20 11:07   ` [Buildroot] [PATCH v2 1/3] qt5: bump version " Julien CORJON

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20150719232202.67a5bc98@free-electrons.com \
    --to=thomas.petazzoni@free-electrons.com \
    --cc=buildroot@busybox.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox