FLTK 1.4 for TC 16

[Juanito]

In armhf, all of them have a gpu, which wayland compositors can use to speed graphics up.

"can use", but does it use GPU acceleration? (taking into account provided GL version 2x)

When there used to be a weston-info I'm pretty sure it showed the gpu was being used.

Edit: about:support on firefox shows (albeit aarch64):

Code: [Select]

GPU #1
Active Yes
Description V3D 4.2.14.0
Vendor ID 0x7640
Device ID 0xaaba
Driver Vendor mesa/v3d
Driver Version 24.2.5.0

[Rich]

Hi Juanito

Using:

Code: [Select]

----- Snip -----
 --disable-xcursor 
 ----- Snip ----- ...

Please don't do that. See here:

... To enable mouse corners,  --enable-xcursor  in  ./configure  and recompile.
libXcursor  is already a dependency for xorg, xvesa, xfbdev, flwm. gtk2, gtk3, ...
The cursors that depend on  libXcursor  are compiled into fltk even with  --disable-xcursor.
I saw no increase in extension size with  --enable-xcursor.

... ..so fltk-1.4.x is substantially larger than fltk-1.3.x ...

That's just the libraries. I wonder how much the apps compiled
against them grow.

... although there is additional functionality, ref https://www.fltk.org/articles.php?L1955+I0+T+P1+Q

Additional functionality is only relevant if it's actually useful and
someone is writing software that employs it.

[yvs]

In armhf, all of them have a gpu, which wayland compositors can use to speed graphics up.

"can use", but does it use GPU acceleration? (taking into account provided GL version 2x)

When there used to be a weston-info I'm pretty sure it showed the gpu was being used.

It can be said surely by running btop:
if there's no additional CPU utilization after (for example) starting 3D-cube test rotation, then it runs on GPU.

Edit: about:support on firefox shows (albeit aarch64):

It was about armhf with overlay supporting GL2 only. On aarch64 - idk (not tested), probably it works with distinct gpu and overlays (if it wasn't software GL4 or GLES path)