I suppose if you're going to be removing the cairo lib, then perhaps it'll be a non-issue ...

Regarding libfltk_cairo: yes. But you'd still need to link to libcairo or not, depending on ... ?

I think the relevant information should be in makeinclude. This defines LINKFLTKCAIRO (w/o embedded underscore) whereas your Makefile defines LINKFLTK_CAIRO (with underscore). Something similar is available for the Cairo compiler flags.

The CMake patch I wrote checks whether FLTK_HAVE_CAIRO is defined (in CMake!) and links in libcairo if true. The if (TARGET ...) check is only to determine if it's the "old style" build (today, with libfltk_cairo) or the future build (w/o libfltk_cairo). When the transition is done this check can be removed.

—
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications on the go with GitHub Mobile for iOS or Android.
You are receiving this because you are subscribed to this thread.Message ID: <fltk/fltk/issues/358/1013956694@github.com>