I understand and am very happy with the current solution.

👍 @jwillikers I'm happy that you are happy.

Thanks for adding those target_include_directories calls for me.

Not only for you. Your report made clear that adding the proper include directories is necessary in general. There may be other systems where some libs and headers can be found in non-system directories.

the only thing that might cause problems is packaging up the FLTKConfig.cmake with the fltk library and installing it on a different machine, ...

I don't think that this is a common scenario. If you link to shared libs on one system and try to run an application on another system you might have much more important (ABI) incompatibilities than only the search paths...

—
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/pull/954/c2069809049@github.com>