DO NOT REPLY TO THIS MESSAGE.  INSTEAD, POST ANY RESPONSES TO THE LINK BELOW.

[STR New]

Link: https://www.fltk.org/str.php?L3409
Version: 1.3.4


I don't think that the described problem is still an issue, but it's hard
to understand which circumstances led to the OP's problem.

I can tell that we changed building the bundled libs to use their own
"prefix" for function names. This makes it possible to use one version of
libpng in FLTK's internals (for images) and using another - incompatible -
libpng in the application or in any shared system libs.

This does even work for loading shared libraries dynamically at runtime.
These "prefixed" bundled libraries solved all kinds of problems with
incompatible image libraries.

Therefore I believe that this STR is no longer relevant (i.e. resolved) in
FLTK 1.4.0, but I can be wrong if the OP had another issue. Finding the
"correct" libs installed on the system should no longer be an issue. It
doesn't matter if we "find" a certain libpng version, it's more about
building FLTK with either the system or the bundled version, and the latter
is definitely fixed.

I suggest to close this STR if the OP (w1hkj) doesn't chime in and explains
why this STR is still relevant.


Link: https://www.fltk.org/str.php?L3409
Version: 1.3.4