@OPNA2608: I created a preliminary branch issue-250_cairoext (beta status) in my fork which you can view and download/pull.

Main difference: the extra Cairo library libfltk_cairo is gone, Cairo is integrated in libfltk if and only if one of the Cairo options (OPTION_CAIRO or OPTION_CAIROEXT) is enabled.

I need a break and I don't know yet whether this is the proper solution. This needs more tests on different platforms.

Excerpt from the relevant commit log:

Static linking is not affected by this change, but users building
with hand-made Makefiles will have to remove libfltk_cairo.

The shared FLTK library libfltk.{so|dylib|dll|..} depends on libcairo
if and only if FLTK is built with one of the Cairo options. This has
always been the case for OPTION_CAIROEXT but is now also true if only
OPTION_CAIRO is selected, i.e. FLTK programs linked with a Cairo
enabled shared FLTK library will also be linked with libcairo.

All feedback and test results would be welcome. TIA.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.