Hi Brad, thanks for keeping answering my emails! >> I always end up with /usr/include/ being the CURSES_INCLUDE_PATH. > > 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. > To ignore the symlinks one could configure with > > -DCURSES_INCLUDE_PATH=/usr/include/ncurses > > to tell FindCurses to skip searching and just use that. Once it has > that directory the computation of the other values may work. While this is true, my expectation are that CMake as the build tool of my choice should be able to figure out its own dependencies without the user to explicitly setting an include path. I opened !3638 to get my issue fixed. We can continue discussion the issue there. Kind regards, Christoph -- Nous vivons une époque où les pizzas arrivent plus vite que la police. [Claude Chabrol] -- 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
