Current CMake on macOS generates /usr/local/FLTK.framework which does not contain any headers or libraries, but is still picked up and preferred over /usr/local/lib/libfltk.dylib. Since the framework is empty, builds fail (i.e. TigerVNC) with fltk library not found.

I've just tried here to build on macOS a client FLTK app with the modern CMake procedure described in README.CMake.txt in 2 ways

• against an installed set of static FLTK libs;
• against an installed set of dynamic FLTK libs.

In both cases, the build is successful and the app runs. The target installation directory was not specified which amounts to /usr/local. In both cases /usr/local/FLTK.frameworkis necessary. The client program's CMakeLists.txt needs a small change between the 2 builds. The static build uses
target_link_libraries(client-name PRIVATE fltk::images)
The dynamic build uses
target_link_libraries(client-name PRIVATE fltk::images-shared)

What is the exact problem hit when building TigerVNC?

—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.Message ID: <fltk/fltk/issues/961/2081417528@github.com>