cvs commit: src/gnu/lib/libreadline/readline Makefile

Andrey Chernov ache at nagual.pp.ru
Mon Oct 18 07:53:45 PDT 2004


On Mon, Oct 18, 2004 at 05:13:02PM +0300, Ruslan Ermilov wrote:
> Crunched binaries don't use whole libraries either.  The many .o
> files just get linked with libraries the usual way.  (Unrelated,
> but I thought I'd mention this anyway...)

The many files may just needs -ltermcap.

> But then perhaps you can tell me where the APIs for libcurses,
> libmytinfo, libtermcap, libtermlib, and libtinfo are documented,
> so one can decide which pseudo-library to link against in our
> case of libncurses?  If you happen to know...  Because I read
> README and it says it implements the System V curses API with
> some extensions, and it doesn't mention any of the above libs.

Usually it is documented in the manpages and in other formats, like 
nroff-based, depending on system. Before ncurses we and all BSDs have 
standard manpages describing termcap functions family and file format for
years. Do you keep some CDs with old BSDs, by chance?
libtermcap = libtermlib, historycally
libmytinfo is for some non-standard stuff, maybe terminfo emulation based 
on termcap, I don't remember exactly now.
Curses implementation can be layer on termcap or on terminfo (or even 
on something else). In later cases it may not provide termcap 
compatibility or do it poorly. SysV curses API standartization effors 
shows up relatively recent, many Unix-likes and others (DOS f.e.) have 
their own not fully SysV API compatible curses-es.

-- 
Andrey Chernov | http://ache.pp.ru/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 305 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/cvs-src/attachments/20041018/dd2faeed/attachment.bin


More information about the cvs-src mailing list