delorie.com/archives/browse.cgi | search |
Charles Wilson wrote: > > Earnie Boyd wrote: > > > > Charles Wilson wrote: > > > > > > I'll release a new ncurses where the ncurses version of unctrl.h is > > > renamed 'nunctrl.h' and change all internal ncurses references to point > > > to the new file. But I can't guarantee any time frame on that. > > > > > > > I don't know about the rest of this list but I would prefer it be > > /usr/include/ncurses/unctrl.h. It is then obvious as to what it is > > for. If you name it nunctrl.h then it won't be that obvious. > > But if I do that, then where should all the other include files for > ncurses go? It's really odd for them to be split between /usr/include > and /usr/include/ncurses/. IMO, yes, even if it is odd, they should be put in /usr/include/ncurses. At least programs won't have to be modified to use the ncurses version of unctrl.h like they would if you renamed it. The correct headers will be used by a simple switch to gcc - see below. > However, ncurses is not like readline -- it > doesn't like to install its header files into a subdirectory of > /usr/include. (e.g. the #include directives for most packages that > depend on ncurses reference <curses.h>, not <ncurses/curses.h>. This > also goes for the ncurses header files themselves -- they > inter-reference <foo.h>, not <ncurses/foo.h> or "foo.h". > This can be handled via CC='gcc -I/usr/include/ncurses' so that the headers in ncurses is found instead of the headers in /usr/include. Cheers, Earnie. _________________________________________________________ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com -- Want to unsubscribe from this list? Check out: http://cygwin.com/ml/#unsubscribe-simple
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |