does not build with any FLTK release

[umlaeute]

giada uses the latest and greatest FLTK git snapshot, and relies on features not available in the last stable FLTK release (at the time of writing this is FLTK-1.3.8 from 2021).

Now I totally understand that wish to use things like SVGs and what not.

Howerver, I also understand that distributions like Debian are not overly keen on shipping anything but released versions of widget libraries like FLTK.

Which leaves me with the problem, that I cannot compile a released version of giada on my Debian system (and with "released version" i mean the "Source code" download from the release page, e.g. https://github.com/monocasual/giada/releases/tag/v0.24.0).

I'm aware that I could just do a git clone to get everything I need, but...

My actual motivation behind all this is that I'm one of the Debian Maintainers of the Debian giada package (which incidentally also become the Ubuntu packages).
For the (Debian-official) Debian packages, I have to rely on what is available in Debian itself.
Most notably

• I cannot clone some arbitrary git repository during the build process
• I cannot use convenience copies of dependencies vendored into a package (just in case you were thinking of providing a Source download that includes FLTK/JUCE/...

Currently this means, that giada in Debian/Ubuntu is stuck at 0.22.0.

If this is undesired from your side, I see the following options:

• Talk the FLTK team into releasing FLTK-1.4 (this would obviously be best; but I have no idea about their release plan)
• Revert the FLTK-dependency to a released version of FLTK (you lose nifty new FTLK- features)
• Provide support for both FTLK-git and FLTK-1.3.8 (you add code complexity, and testing becomes more complicated)
• Remove giada from Debian (from my POV the worst option)

[Apteryks]

I'd also be interested in allowing the use of system-provided dependencies such as fltk and juce, for the same reasons (packaging for GNU Guix).

[gvnnz]

Hi @umlaeute and @Apteryks , I understand your pain.

Now I totally understand that wish to use things like SVGs and what not.

That was indeed our motivation for switching to the git submodule approach. Luckily the FLTK team will release FLTK 1.4 pretty soon (as far as I know). When that happens, the FLTK dependency will be reverted back to be a simple external dependency as any other third party libs we use (libsdnfile, ... - except for JUCE sadly).

Thanks for your patience!