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
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)curse
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 wi
Hi Brad,
thank you for pointing out the conditions. But they cannot be used to
ignore the symolic link in /usr/include/ to favor the acutal header in
/usr/include/ncurses/. I always end up with /usr/include/ being the
CURSES_INCLUDE_PATH.
> On 7/28/19 4:21 PM, Christoph Grüninger wrote:
>> -includ
On 7/28/19 4:21 PM, Christoph Grüninger wrote:
> -include_directories(${CURSES_INCLUDE_PATH})
> +include_directories(${CURSES_INCLUDE_PATH}/ncurses/)
Why is that needed given the conditions here:
https://gitlab.kitware.com/cmake/cmake/blob/v3.15.1/Source/CursesDialog/form/form.h#L38-57
http
