[Top][All Lists]

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

Re: Insalling both wide and normal ncurses

From: Thomas Dickey
Subject: Re: Insalling both wide and normal ncurses
Date: Mon, 27 Aug 2007 19:02:57 -0400 (EDT)

On Mon, 27 Aug 2007, Michail Vidiassov wrote:

Dear Thomas (and All),

what is the recommended steps if one want to have both wide and
normal versions of ncurses installed, normal being the default (and not fixing the programs to look into ncurses/ncursesw for header files)?

As far as I can see, the following is to be done:
configure with --enable-widec --enable-overwrite
delete libcurses symlink to libncursesw
configure with --without-progs --mandir=/something/tempotrarry1

I suppose so - the "--without-progs" can solve some problems.
Technically those do not care which of the libraries they are linked
against, since they use the lower-level calls that do not depend on
the wide-character support.  At least one packager is using the
"--with-termlib" option to make that part a separate library.

--includedir=/something/tempotrary2 install
delete temporary dirs with duplicate mans and non-wide header files
create libcurses link to libncurses

Any suggestions?

BTW, the fact that --enable/disable-overwrite affects both libcurses link and header files location seems to me to be somewhat confusing.

It's supposed to install a different symbolic link for the library (I just checked, and it seems to work). The headers can point to the same file (the one installed for ncursesw is supposed to contain all of the definitions used in the one for ncurses).

With all of that, it's possible that I have overlooked something.
Is there some case where the --enable-overwrite results are not
working as they are "supposed to"?

Thomas E. Dickey

reply via email to

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