cvs commit: src/share/mk bsd.libnames.mk src/lib/bind config.mk
src/lib/bind/bind Makefile src/lib/bind/bind9 Makefile
src/lib/bind/dns Makefile src/lib/bind/isc Makefile src/l
Bjoern A. Zeeb
bzeeb-lists at lists.zabbadoz.net
Fri Sep 24 15:15:09 PDT 2004
On Fri, 24 Sep 2004, Ruslan Ermilov wrote:
> Don't expose BIND libraries and their headers to the public by default,
> but have a knob (WANT_BIND_LIBS) to build and install them in /usr/lib
> and /usr/include. Rumors are that this may be useful at a later point,
> let's see.
can you please be more precise ?
> What this really means is that all BIND libraries are now internal to
> buildworld (by default, unless WANT_BIND_LIBS is defined), and linked
> statically into various BIND executables.
these days that there is a dynalically linked base system why do it
the opposite way ? I am just curious ;-)
Also I would be interested in the difference of size this makes if you
build statically vs. dynamically and in both ways install all binaries
(plus libraries in the dyn case) ?
Most likely this will no longer be intersting once I understand why we
do it that way so perhaps postpone this answer just to save you the
Bjoern A. Zeeb bzeeb at Zabbadoz dot NeT
More information about the cvs-all