From 31bc465ed7c22db3ff44e5ca942711f458f46178 Mon Sep 17 00:00:00 2001 From: giraffedata Date: Tue, 23 Feb 2010 15:53:59 +0000 Subject: Improve explanation of merge build git-svn-id: http://svn.code.sf.net/p/netpbm/code/trunk@1128 9d0c8265-081b-0410-96cb-a4ca84ce46f8 --- doc/INSTALL | 9 +++++---- 1 file changed, 5 insertions(+), 4 deletions(-) diff --git a/doc/INSTALL b/doc/INSTALL index ec2cfbed..9412b296 100644 --- a/doc/INSTALL +++ b/doc/INSTALL @@ -259,10 +259,11 @@ and which one is default is controlled by the DEFAULT_TARGET make variable in config.mk, and its value is one of the choices you make via the Configure dialog. -The standard build is the conventional one. The merge build is a way -to reduce disk space and other resource usage in some configurations. -These are rare configurations, mostly antique ones. The advent of -shared libraries largely obsoleted the merge build. +The standard build is the conventional one. The merge build is a way to +reduce disk space and other resource usage in some configurations. These are +rare configurations, mostly antique ones. The advent of shared libraries +largely obsoleted the merge build. In some configurations, Netpbm uses _more_ +resources with the merge build. In the standard build, hundreds of separate programs get built: ppmtogif, pamcomp, etc. -- cgit 1.4.1