new fltk

[willysr]

It seems next slackware will introduce new fltk which has different .so version

should we try to bump fltk in SBo to the same version as in current to test whether all the scripts that depends on this will build or not. It can help us to identify which scripts which will not work with newer version and consider to patch or remove it during next cycle.

any suggestion @aclemons @Ponce ?

[Ponce]

I was pondering... what if it gets updated again (and again, and again...) before we close submissions?

[willysr]

i would say 1.4.x is safe to use for now, unless Pat decided to go with 1.5 in the future

FLTK 1.4 is intended to be mostly API compatible with FLTK 1.3.x so you don't need to change source code when you upgrade to FLTK 1.4. However, all programs must be recompiled with FLTK 1.4 because the ABI (Application Binary Interface) has changed.
The current development branch for FLTK 1.5 on GitHub [2] is master. FLTK 1.4 is in maintenance mode and will get only serious bug fixes in git branch branch-1.4.

[willysr]

Oh, i'm targeting for 15.1, so it won't be merged into master so soon, unless we are sure that everything works fine with 1.4 in SBo

[willysr]

• academic/OpenVSP
• academic/gmsh
• academic/lalnview
• academic/seaview
• [❌ ] academic/treebest-ensembl (last update in 2019 and no further development upstream) -> proposed to be deleted
• audio/alsamixergui
• audio/butt
• audio/horgand
• audio/lmms
• [❌ ] audio/rakarrack (last update was in 2010) -> proposed to be deleted
• audio/sfc
• audio/tapiir
• audio/vocoder
• audio/yoshimi
• audio/zynaddsubfx
• games/eureka
• games/oblige
• games/oblige-legacy4
• graphics/Pixie
• graphics/flpsed
• graphics/posterazor
• graphics/tuxpaint
• ham/fldigi
• ham/flrig
• [❌ ] libraries/edelib (last update was in 2014) -> proposed to be deleted
• libraries/spandsp
• network/dillo (no merged yet but it's tracked in How can I build this with FLTK 1.4 dillo-browser/dillo#370)
• office/htmldoc
• python/pyfltk
• system/xdiskusage

[willysr]

I'm looking at some of the scripts and the first three failed to build with new fltk 1.4.4 saying it can't find cairo.h when the script is matched with how current works
Also, when I looked at gmsh, I found this

binary builds use FLTK 1.3 (instead of FLTK 1.4, which introduced performance regressions in OpenGL rendering

[Ponce]

that's not reassuring...

I'll try to have a look when I'll get back from holidays (3 weeks or so ;-) )!

[willysr]

@linrs we should continue our discussion here because the other issue will be filled with bot build output

so basically disabling cairo will let us build some scripts, but it cause build errors in other scripts.

[willysr]

@aclemons is it possible to use hints to give build parameters for fltk to enable/disable cairo for each scripts?
so like appA needs ftlk with cairo disabled so we can give hint to build with fltk without cairo

[aclemons]

Not currently possible since I treat the whole repo as one set. It would need to distinct repos with a set of hints for each

[willysr]

I'm thinking of having 2 fltk with cairo enabled/disabled but it would be nightmare to maintain it.

[linrs]

@LinRs we should continue our discussion here because the other issue will be filled with bot build output

so basically disabling cairo will let us build some scripts, but it cause build errors in other scripts.

Since upstream will remove the '--enable-cairo' option, it is not necessary to maintain 2 fltk.
https://github.com/fltk/fltk/blob/release-1.4.4/cairo/cairo_dummy.c#L17-L24
fltk/fltk@b252e5e#diff-98f8cbc0a9bf1ff3eb1408aa985cc3652b3d3a5a6389270e75570681a52f1ca6L828-R831

I am afraid that certain could not be built with FLTK 1.4.x whether disabling cairo or not, as they are either unmaintained by upstream or upstream developers are not aware of the new FLTK.

Some need to be updated to the latest version, as upstream has released with fixes for FLTK 1.4.x:
academic/seaview -> 5.1
audio/yoshimi -> 2.3.4.1

Some need to change the compiling flags:
games/eureka: upstream treated warning as error, so removing "-Werror" is enough.

[willysr]

That's good to know, i will update the list above