From: Peter Seiderer <ps.report@gmx.net>
To: "Tomaž Smodiš" <tomazsmodis73@hotmail.com>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] buildroot EGLFS support
Date: Mon, 24 Jan 2022 23:34:05 +0100 [thread overview]
Message-ID: <20220124233405.250ab307@gmx.net> (raw)
In-Reply-To: <VI1PR03MB36771B6256EEB933FE5C7DDDA95E9@VI1PR03MB3677.eurprd03.prod.outlook.com>
Hello Tomaž,
On Mon, 24 Jan 2022 16:28:00 +0100, Tomaž Smodiš <tomazsmodis73@hotmail.com> wrote:
> Hi
>
> With help of Mr. Richard Ash I managed to build my buildroot Os.
>
> With the same compiler I buidl/compiled Qt libraries against buildroot
> sysroot.
Why compile outside of buildroot? Qt is well integrated into buildroot
(as Richard already pointed out [1])...
>
> I was finally able to run some cpp code. I successfully ran Qt console
> application.
>
> However if I try to run Qt GUI Application I got errors. I enabled eglfs
> support in menuconfig:
>
> In target packages, graphic libraries and applications I enabled mesa3d
> option Gallium swrast driver and OpenGL EGL and OpenGL ES options.
Why swrast and not 'Gallium vc4 driver'?
>
> I ran make successfully, deployed to Raspberry Pi 3 b+ but after I run
> my app with:
>
> strace ./myapp -platform eglfs
>
> I got errror:
>
> write(2, "EGL library doesn't support Emul"..., 48EGL library doesn't
> support Emulator extensions
>
> Any advice?
My 'standard' RPi3 (64-bit) buildroot test configuration is like the following:
BR2_aarch64=y
BR2_ARM_FPU_VFPV4=y
BR2_OPTIMIZE_3=y
BR2_TOOLCHAIN_BUILDROOT_GLIBC=y
BR2_PACKAGE_HOST_LINUX_HEADERS_CUSTOM_5_10=y
BR2_PACKAGE_GLIBC_UTILS=y
BR2_GCC_VERSION_11_X=y
BR2_TOOLCHAIN_BUILDROOT_CXX=y
BR2_ROOTFS_DEVICE_CREATION_DYNAMIC_EUDEV=y
BR2_SYSTEM_DHCP="eth0"
BR2_GENERATE_LOCALE="en_US"
BR2_ROOTFS_POST_BUILD_SCRIPT="board/raspberrypi3-64/post-build.sh"
BR2_ROOTFS_POST_IMAGE_SCRIPT="board/raspberrypi3-64/post-image.sh"
BR2_LINUX_KERNEL=y
BR2_LINUX_KERNEL_CUSTOM_TARBALL=y
BR2_LINUX_KERNEL_CUSTOM_TARBALL_LOCATION="$(call github,raspberrypi,linux,0b54dbda3cca2beb51e236a25738784e90853b64)/linux-0b54dbda3cca2beb51e236a25738784e90853b64.tar.gz"
BR2_LINUX_KERNEL_DEFCONFIG="bcmrpi3"
BR2_LINUX_KERNEL_DTS_SUPPORT=y
BR2_LINUX_KERNEL_INTREE_DTS_NAME="broadcom/bcm2710-rpi-3-b broadcom/bcm2710-rpi-3-b-plus broadcom/bcm2837-rpi-3-b"
BR2_LINUX_KERNEL_NEEDS_HOST_OPENSSL=y
BR2_PACKAGE_STRACE=y
BR2_PACKAGE_DEJAVU=y
BR2_PACKAGE_MESA3D=y
BR2_PACKAGE_MESA3D_GALLIUM_DRIVER_VC4=y
BR2_PACKAGE_MESA3D_OPENGL_ES=y
BR2_PACKAGE_QT5=y
BR2_PACKAGE_QT5BASE_EXAMPLES=y
BR2_PACKAGE_QT5BASE_OPENGL_LIB=y
BR2_PACKAGE_QT5BASE_EGLFS=y
BR2_PACKAGE_QT5BASE_DEFAULT_QPA="eglfs"
BR2_PACKAGE_QT5BASE_FONTCONFIG=y
BR2_PACKAGE_QT5BASE_HARFBUZZ=y
BR2_PACKAGE_QT5BASE_GIF=y
BR2_PACKAGE_QT5BASE_JPEG=y
BR2_PACKAGE_QT5BASE_PNG=y
BR2_PACKAGE_QT5QUICKCONTROLS=y
BR2_PACKAGE_QT5QUICKCONTROLS2=y
BR2_PACKAGE_RPI_FIRMWARE=y
BR2_PACKAGE_RPI_FIRMWARE_BOOTCODE_BIN=y
BR2_PACKAGE_RPI_FIRMWARE_VARIANT_PI=y
BR2_PACKAGE_RPI_FIRMWARE_CONFIG_FILE="board/raspberrypi3-64/config_3_64bit.txt"
BR2_TARGET_ROOTFS_EXT2=y
BR2_TARGET_ROOTFS_EXT2_4=y
BR2_TARGET_ROOTFS_EXT2_SIZE="384M"
# BR2_TARGET_ROOTFS_TAR is not set
BR2_PACKAGE_HOST_DOSFSTOOLS=y
BR2_PACKAGE_HOST_GENIMAGE=y
BR2_PACKAGE_HOST_MTOOLS=y
Needs only the added 'dtoverlay=vc4-kms-v3d' to the boot-partition
config.txt file, most provided Qt gui examples run fine, e.g.
/usr/lib/qt/examples/gui/analogclock/analogclock
or
/usr/lib/qt/examples/quickcontrols2/gallery/gallery
etc.
Regards,
Peter
[1] http://lists.busybox.net/pipermail/buildroot/2022-January/634093.html
>
> kind regards Thomas
>
> _______________________________________________
> buildroot mailing list
> buildroot@buildroot.org
> https://lists.buildroot.org/mailman/listinfo/buildroot
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2022-01-24 22:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-24 15:28 [Buildroot] buildroot EGLFS support Tomaž Smodiš
2022-01-24 22:34 ` Peter Seiderer [this message]
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=20220124233405.250ab307@gmx.net \
--to=ps.report@gmx.net \
--cc=buildroot@buildroot.org \
--cc=tomazsmodis73@hotmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.