[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: headers installed incorrectly?
From: |
Bob Rossi |
Subject: |
Re: headers installed incorrectly? |
Date: |
Thu, 3 Aug 2006 19:54:17 -0400 |
User-agent: |
Mutt/1.5.11 |
On Thu, Aug 03, 2006 at 11:42:23PM +0000, Alexey Toptygin wrote:
> On Thu, 3 Aug 2006, Thomas Dickey wrote:
>
> >>My problem is that make install then put all the headers under
> >>/usr/local/include/ncurses, but it generated the internal includes as
> >>ncurses/whatever.h. So, if I use -I/usr/local/include/ncurses, gcc can't
> >>find the ncurses/unctrl.h (among others) that is included from ncurses.h.
> >>I have to have both -I/usr/local/include/ncurses and -I/usr/local/include
> >>in order to make it work. Is this a bug?
> >
> >no, it's a feature. The headers are in a subdirectory to make it simple
> >to avoid including /usr/include/curses.h
> >
> >Portable applications that use ncurses would either have two -I options
> >or have some ifdef to switch between these cases:
> >
> > #include <curses.h>
> > #include <ncurses/curses.h>
> > #include <ncursesw/curses.h>
>
> Does this mean I should be filing bug reports to authors of software that
> only test for ncurses.h and curses.h in their configure scripts? Should
> they all be testing for ncurses/curses.h first?
Hi Alexey,
I have CGDB only check for curses.h. This has worked everywhere so far
that I have built it. Usually it's a symlink.
Bob Rossi