Richard Wackerbarth wrote:
I thought that setting the CURSES_LIBRARY was the method by which
"CMake will use ncurses"
But, at least on this machine, ncurses has installed the header /usr/
local/include/ncurses.h rather than /usr/local/include/curses.h .
Does this mean that the ncurses installation is also "broken"?
Or should the CMake code have some "#if" to decide which header to
include?
We would have to check the official curses interface specification to
know the "right" fix. However, if your system comes with curses and
ncurses installed this way we should be able to support it without much
trouble. Please submit a bug report here:
http://www.cmake.org/Bug
Meanwhile you can work around the problem by hacking the source yourself
before building or creating your own "curses.h" that just includes
"ncurses.h".
-Brad
_______________________________________________
CMake mailing list
[email protected]
http://www.cmake.org/mailman/listinfo/cmake
