Fix section numbering for new sections (due to TOC kludge).

[privoxy.git] / doc / source / buildsource.sgml

diff --git a/doc/source/buildsource.sgml b/doc/source/buildsource.sgml
index d180c02..3c09f25 100644 (file)
--- a/doc/source/buildsource.sgml
+++ b/doc/source/buildsource.sgml
@@ -3,7 +3,7 @@
 
  Purpose     :  Entity included in other project documents.
                 
- $Id: buildsource.sgml,v 1.1 2002/04/04 06:48:37 hal9 Exp $
+ $Id: buildsource.sgml,v 1.6 2002/04/26 05:25:23 hal9 Exp $
 
  Written by and Copyright (C) 2001 the SourceForge
  Privoxy team. http://www.privoxy.org/
@@ -28,27 +28,28 @@
 -->
 
 <para>
- There are several ways to install <application>Privoxy</application>.
+ To build <application>Privoxy</application> from source, 
+ autoheader, autoconf, <ulink
+ url="http://www.gnu.org/software/make/make.html">GNU make
+ (gmake)</ulink>, and, of course, a C compiler are required.
 </para>
 
 <para>
- To build <application>Privoxy</application> from source, 
- autoconf and GNU make (gmake) are required. Source is available as gzipped
- tar archives. For this, first unpack the source: 
+ When building from a source tarball (either release version or
+ nightly CVS tarball), first unpack the source: 
 </para>
 
 <para>
  <screen>
  tar xzvf privoxy-&p-version;<![%p-not-stable;[-beta]]>-src* [.tgz or .tar.gz]
  cd privoxy-&p-version;<![%p-not-stable;[-beta]]>
- </screen>
+</screen>
 </para>
 
-
 <para>
- For retrieving the current CVS sources, you'll need the CVS 
- package installed first. Note CVS source is development quality, 
- and may not be stable, or well tested. To download CVS source:
+ For retrieving the current CVS sources, you'll need CVS installed.
+ Note that sources from CVS are development quality, and may not be
+ stable, or well tested. To download CVS source:
 </para>
 
 <para>
@@ -56,7 +57,7 @@
   cvs -d:pserver:anonymous@cvs.ijbswa.sourceforge.net:/cvsroot/ijbswa login
   cvs -z3 -d:pserver:anonymous@cvs.ijbswa.sourceforge.net:/cvsroot/ijbswa co current
   cd current
- </screen>
+</screen>
 </para>
 
 <para>
@@ -72,24 +73,37 @@
  <screen>
  autoheader
  autoconf
- ./configure      (--help to see options)
- make             (the make from gnu, gmake for *BSD) 
+ ./configure      # (--help to see options)
+ make             # (the make from gnu, gmake for *BSD) 
  su 
- make -n install  (to see where all the files will go)
- make install     (to really install)
- </screen>
+ make -n install  # (to see where all the files will go)
+ make install     # (to really install)
+</screen>
+</para>
+
+<para>
+  If you have gnu make, you can have the first four steps 
+  automatically done for you by just typing:
+</para>
+
+<para>
+ <screen>
+  make
+</screen>
+</para>
+
+<para>
+  in the freshly downloaded or unpacked source directory.
 </para>
 
 <para>
- Redhat and SuSE src and binary RPMs can be built with 
- <quote><command>make redhat-dist</command></quote> or
- <quote><command>make suse-dist</command></quote> from unpacked sources. You
- will need to run <quote><command>autoconf; autoheader;
- ./configure</command></quote> beforehand. *BSD will require gmake (from
- <ulink url="http://www.gnu.org">http://www.gnu.org</ulink>). 
- <![%p-readme;[See the user-manual for OS/2 build instructions.]]>
+ For more detailed instructions on how to build Redhat and SuSE RPMs,
+ Windows self-extracting installers, building on platforms with
+ special requirements etc, please consult the <ulink
+ url="../developer-manual/newrelease.html">developer manual</ulink>.
 </para>
 
+<!-- print for README only -->
  <![%p-readme;[
  <para>
   For binary RPM installation, and other platforms, see the user-manual