[yocto] [meta-raspberrypi][PATCH v3] qtbase: enable Raspberry Pi support
Martin Jansa
martin.jansa at gmail.com
Mon Oct 26 04:44:07 PDT 2015
On Mon, Oct 26, 2015 at 09:49:54PM +1100, Jonathan Liu wrote:
> [Support #16]
>
> Signed-off-by: Jonathan Liu <net147 at gmail.com>
> ---
> recipes-qt/qt5/qtbase_%.bbappend | 8 ++++++++
> 1 file changed, 8 insertions(+)
> create mode 100644 recipes-qt/qt5/qtbase_%.bbappend
>
> diff --git a/recipes-qt/qt5/qtbase_%.bbappend b/recipes-qt/qt5/qtbase_%.bbappend
> new file mode 100644
> index 0000000..b20138a
> --- /dev/null
> +++ b/recipes-qt/qt5/qtbase_%.bbappend
> @@ -0,0 +1,8 @@
> +PACKAGE_ARCH_rpi = "${MACHINE_ARCH}"
This makes all other qt* recipes (and everything which depends on them)
also MACHINE_ARCH, you can use this code from qt5.inc:
# If Qt5 (qtbase) is machine specific, then everything will be,
# because the (initial) qtbase configuration becomes part of Qt5/qmake
python __anonymous() {
barch = d.getVar("BUILD_ARCH", True) or ''
tarch = d.getVar("TARGET_ARCH", True) or ''
# do not do anything if we are building a native package
if barch != tarch:
tarch = d.getVar("QT_PACKAGES_ARCH", True) or ''
if tarch:
d.setVar("PACKAGE_ARCH", tarch)
}
and set QT_PACKAGES_ARCH to cover at least the recipes which are using
qt5.inc (not the qt5 apps and other recipes).
That's why I didn't like the idea of making it MACHINE_ARCH in the first
place (even though I understand there are cases where is no choice).
> +
> +do_configure_prepend_rpi() {
> + cat > ${S}/mkspecs/oe-device-extra.pri << 'EOF'
> +EGLFS_DEVICE_INTEGRATION = eglfs_brcm
> +QMAKE_LIBS_EGL = -lEGL -lGLESv2
> +EOF
> +}
> --
> 2.6.1
>
> --
> _______________________________________________
> yocto mailing list
> yocto at yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
--
Martin 'JaMa' Jansa jabber: Martin.Jansa at gmail.com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 181 bytes
Desc: Digital signature
URL: <http://lists.yoctoproject.org/pipermail/yocto/attachments/20151026/7ef02596/attachment.pgp>
More information about the yocto
mailing list