jogamp - Re: What is the status of font rendering with JOGL?

jogamp › jogl

Re: What is the status of font rendering with JOGL?

Posted by Xerxes Rånby on May 29, 2019; 5:45pm
URL: https://forum.jogamp.org/What-is-the-status-of-font-rendering-with-JOGL-tp4039805p4039818.html

Yocto and Buildroot are both good tools if you want to bring up a working system and a build environment for embedded systems from sourcecode. When using Yocto or Buildroot the whole build can be done deterministic.

I have tested to use Buildroot to compile custom aarch64 rasperry pi 3 systems with minimal footprint with OpenGL support using the mesa vc4 drivers directly from eaarly init after Linux is loaded by using the Linux kernel modesetting drm-kms driver api.

I explored the possibility to run Jogamp on the Linux kernel modesetting drm-kms api however it require some new ways to initialize EGL in Jogl because the drm-kms api did not work with EGL default device instead you had to initialize EGL using an extension.
eglGetPlatformDisplayEXT(EGL_PLATFORM_GBM_KHR, gbm->dev, NULL);
https://gitlab.freedesktop.org/mesa/kmscube
https://gitlab.freedesktop.org/mesa/kmscube/blob/master/common.c#L164-235

Sven Gothel wrote

On 5/29/19 6:26 PM, Xerxes Rånby [via jogamp] wrote:
> The Gentoo Rpi3 64bit includes full OpenGL acceleration including the 7"
> touchscreen out of the box. sakaki- who maintains this Gentoo image have done
> a superb job.
> https://github.com/sakaki-/gentoo-on-rpi3-64bit
> JogAmp runs on 64bit arm using this Gentoo image.
>
> Fedora aarch64 did work fine with HDMI and OpenGL however the 7" TFT did not
> work last time i tested.
> https://fedoraproject.org/wiki/Architectures/ARM/Raspberry_Pi
>
> Debian have some test images for aarch64 but they require a lot of manual
> setup before you can use them with OpenGL:
> https://wiki.debian.org/RaspberryPi3
>
> Arch linux also have Raspberry Pi aarch64 support with some manual setup.
> https://archlinuxarm.org/platforms/armv8/broadcom/raspberry-pi-3

Thank you.

So I assume Gentoo and Arch Linux expose the newest software versions?

Further I intend to use encapsulated OS images
for building and testing the binaries
for the purpose of having a SHA256 defined build system
to ensure SCC identity (known build environment + sources).
<http://jogamp.org/wiki/index.php?title=SW_Tracking_Report_Feature_Objectives_Overview#Source_Certification_Contract_.28SCC.29>

To all: What would be the easiest and best encapsulation?
In a way a chroot would suffice :)
Surely not so easy on the Windows/OSX side of the medal.
Not a too pressing thing, but a nice to have.
Will update myself about it after 2.4.0.

Probably should create discussion threads for each,
so, all please forgive me for brainstorming.

~Sven