@ggarra13 Do I understand this correctly? You say that the FLTK build reads FLTK header files "first" from its future install location (CMAKE_INSTALL_PREFIX), i.e. from a previous build (if it exists) and only then (i.e. if not found) from its own source ("checkout") directory, but this is caused by setting CMAKE_PREFIX_PATH and CMAKE_INSTALL_PREFIX to the same directory?

Since you also say that you need to rm -rf $BUILD_DIR/include/FL this implies that the first build succeeds as expected, and a following build (with updated FLTK sources) would potentially fail because the build uses the header files of the previous build (if not deleted). Is this correct?

AFAICT the FLTK build sets the compiler include path(s) such that its own build directory comes first, i.e. before its own source directory. I'm not sure how CMAKE_PREFIX_PATH and CMAKE_INSTALL_PREFIX interact with this while building FLTK. Are you really sure that this is really the case?

Please do the following or something similar to verify this and post the commandline of the compile command requested below together with your full real paths:

1. Build FLTK as usual (we don't need any output from this successful build)
2. touch exactly one FLTK source file: touch src/Fl_Tabs.cxx
3. Build FLTK again, using cmake --build <build_dir> --verbose or something else that outputs the commandline

This should display the compiler commandline of Fl_Tabs.cxx. We want only that one file to be changed to see only one compile command. Please post this command here (skip following commands if any).

Thank you Albrecht and sorry for drawing you insane with CMake requests 👍

Welcome, I always appreciate all input. Users often do things differently than devolopers expect, and it's good to see this before the release is done.

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