bug-ncurses
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Cone 0.57 now available.


From: Sam Varshavchik
Subject: Re: Cone 0.57 now available.
Date: Tue, 13 Jan 2004 19:11:18 -0500

Thomas Dickey writes:

On Tue, 13 Jan 2004, Sam Varshavchik wrote:

Thomas Dickey writes:

>
> 20030607
>         + simplify ifdef for bool declaration in curses.h.in (suggested by
>           Albert Chin-A-Young).
>
> (which isn't recent).  I'll change that (thanks).
>
> Cone, btw, needs some work on its configure script (it didn't find the
> header files for ncursesw, added -Wall to $CPPFLAGS, and got confused when
> I set $LIBS and $CPPFLAGS explicitly).

Cone's configure script relies on the compiler's default search path to find
include files, and stuff.  It doesn't lug around its own list of default
directories to poke.

It's going to have to get used to the notion that ncursesw's headers may
be in <ncursesw/xxxx> (and that there may be a /usr/include/curses.h
but /usr/local/lib/libncursesw.a which is unrelated).

Well, at least two out of three are applicable for FC1. The FC1 script only needs to do this:

CPPFLAGS="-I /usr/include/ncursesw"
export CPPFLAGS

That's it. Fedora Core 1 puts narrowchar includes in /usr/include/ncurses, widechar includes in /usr/include/ncursesw, symlinks curses.h and ncurses.h to ncurses/curses.h, and puts both libraries in /usr/lib.

I don't know if I should start assuming where things live. Someone might decide to build a widechar-only curses, and put it in /usr/include. I think it's much safer to stick to the compiler defaults and let people specify the directories themselves.

Attachment: pgphHjjytwAzm.pgp
Description: PGP signature


reply via email to

[Prev in Thread] Current Thread [Next in Thread]