[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Fri, 31 Aug 2007 06:28:58 -0400 (EDT)
On Fri, 31 Aug 2007, Michail Vidiassov wrote:
On Thu, 30 Aug 2007, Thomas Dickey wrote:
in my system (Mac OS X) there is a symlink to libncurses
dynamic library called libtermcap (in /usr/lib, system location).
If I intend to have both wide and non-wide libraries installed,
I have to compile wide curses without --enable-termcap,
non-wide with --enable-termcap and make that symlink, right?
I _think_ you could make the libtermcap link to either library.
Do I get it right that I can install with --enable-widec --enable-overwrite
--enable-termcap and make symlink libncuresew to
libtermcap, libcurses and all other wide libraries to their non-wide names
(and not bother with installing non-wide curses at all) ?
yes (I expect that a small fraction of packagers will do this)
BTW, what is the reason for not making the link libcurses->libncursesw
even if asked for with --enable-overwrite?
Maintaining binary compatibility if _really_ overwriting system libraries?
If you overwrite shared system libraries with an incompatible ABI, you run
the risk of breaking some applications...
Thomas E. Dickey