Re: install.libs dependency in includes directory

[Thomas Dickey]

On Fri, Feb 01, 2002 at 07:53:15PM -0600, Albert Chin wrote:
> includes/Makefile has the following dependency generated by
> aclocal.m4:
>   install \
>   install.libs \
>   install.includes :: $(AUTO_SRC) $(DESTDIR)$(includedir) \
>                   term.h \
>                   curses.h \
>                   unctrl.h \
>                   termcap.h \
>                   $(srcdir)/ncurses_dll.h
>                 ...
> 
> Why does installing the libraries automatically install the include
> files? I know it seems somewhat obvious but as both install.libs and
> install.includes exists, my preference is to leave it to the user
> doing the install.

way-back-when it was implemented, there weren't distributions making separate
runtime and development packages.  So it didn't make sense to distribute the
libraries without the headers.

That was before shared libraries were properly supported on Linux.

Actually, I'm used to doing a make install.libs to get both pieces, e.g., for
ncursesw where I don't want/need a duplicate set of utilities.  I'm not sure
how much impact it would be on packagers (well, Linux anyway - some other
packagers seem to have a not-invented-here attitude regarding the configure
script and associated makefiles).

-- 
Thomas E. Dickey <address@hidden>
http://invisible-island.net
ftp://invisible-island.net