From fcd2f5273fd1b55d505e428d628bf6094421c283 Mon Sep 17 00:00:00 2001
From: simonpj <unknown>
Date: Tue, 27 May 2003 11:06:41 +0000
Subject: [PATCH] [project @ 2003-05-27 11:06:41 by simonpj] Advise against
 SplitObjs for Win32

---
 docs/building/building.sgml |   14 ++++++++++++++
 1 file changed, 14 insertions(+)

diff --git a/docs/building/building.sgml b/docs/building/building.sgml
index 27e390b..f7d3217 100644
--- a/docs/building/building.sgml
+++ b/docs/building/building.sgml
@@ -1721,6 +1721,9 @@ $ make install
       includes <filename>build.mk</filename> after
       <filename>config.mk</filename>.)</para>
 
+     <para>For your convenience, there's a file called <filename>build.mk.sample</filename>
+     that can serve as a starting point for your <filename>build.mk</filename>.</para>
+
       <para>For example, <filename>config.mk.in</filename> contains
       the definition:</para>
 
@@ -4472,6 +4475,17 @@ you'll have to do something more like:
 </para>
 </listitem>
 
+<listitem><para> You almost certainly want to set
+<programlisting>
+  SplitObjs = NO
+</programlisting>
+in your <filename>build.mk</filename> configuration file (see <xref linkend="sec-build-config">).
+This tells the build system not to split each library into a myriad of little object files, one
+for each function.  Doing so reduces binary sizes for statically-linked binaries, but on Windows
+it dramatically increases the time taken to build the libraries in the first place.
+</para>
+</listitem>
+
 <listitem><para> Do not attempt to build the documentation.
 It needs all kinds of wierd Jade stuff that we haven't worked out for
 Win32.</para></listitem>
-- 
1.7.10.4