@MatthiasWM @ManoloFLTK Thanks to both of you for taking care of this.

I agree with Manolo that we can and should(!) remove the pseudo framework from our CMake build and install the config file in a proper place instead. That way everything that needs FLTK can build properly using the FLTKConfig.cmake file in CMake CONFIG mode. Maybe that's what TigerVNC does "wrong", i.e. not using CONFIG mode explicitly but just using find_package(FLTK ...) ?

Then we will keep it that way for now. I'll check what the best cmake compatible location for the config files would be.

It should probably be somewhere below the install prefix in 'share' or 'share/FLTK' or something like that. The CMake docs describe where "packages" (and config files) should be installed, i.e. where the standard search tries to find them.

—
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/2081563757@github.com>