On 8/1/19 6:35 PM, Christoph Grüninger wrote: >> Why is that wrong? As you said it has both `ncurses.h` and `curses.h`. >> Even though they are symlinks one can still use them to compile. > > CMake includes form.h, not (n)curses.h. So form.h is later not found, > because after finding (n)curses.h in /usr/include the search is over.
Ah! CMake's bundled `Source/CursesDialog/form/form.h` which I linked earlier in this thread has all the logic to select the proper curses header to include based on the FindCurses result. However, IIUC you are actually building with `CMAKE_USE_SYSTEM_FORM` enabled so that CMake's `form.h` is not used. This is actually a bug in our handling of `CMAKE_USE_SYSTEM_FORM`. When that is turned on we should be looking for the location of `form.h` rather than `*curses.h`. Please open an issue tracker entry for this. -Brad -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services to support the CMake community. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: https://cmake.org/mailman/listinfo/cmake-developers
