On 7/30/19 4:57 PM, Christoph Grüninger wrote: > 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. 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. >> That said, it's bad that the mess of conditions in the code I linked above >> is even needed to use FindCurses. It would be nice to add a policy to >> change the FindCurses module to work in a more sane way. > > Yes, this would be nice. We have an open issue for this: https://gitlab.kitware.com/cmake/cmake/issues/16392 -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
