[cmake-developers] ncurses sub-dir and include path

Brad King brad.king at kitware.com
Wed Jul 31 09:36:30 EDT 2019


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


More information about the cmake-developers mailing list