2 File : $Source: /cvsroot/ijbswa/current/doc/source/buildsource.sgml,v $
4 Purpose : Entity included in other project documents.
6 $Id: buildsource.sgml,v 1.9.2.1 2002/08/25 17:10:55 hal9 Exp $
8 Copyright (C) 2001, 2002 Privoxy Developers <developers@privoxy.org>
11 ======================================================================
12 This file used for inclusion with other documents only.
13 ======================================================================
15 If you make changes to this file, please verify the finished
16 docs all display as intended.
18 This file is included into:
27 To build <application>Privoxy</application> from source,
28 <ulink url="http://www.gnu.org/software/autoconf/autoconf.html">autoconf</ulink>,
30 url="http://www.gnu.org/software/make/make.html">GNU make
31 (gmake)</ulink>, and, of course, a C compiler like <ulink
32 url="http://www.gnu.org/software/gcc/gcc.html">gcc</ulink> are required.
36 When building from a source tarball (either release version or
38 url="http://cvs.sourceforge.net/cvstarballs/ijbswa-cvsroot.tar.gz">nightly CVS
39 tarball</ulink>), first unpack the source:
44 tar xzvf privoxy-&p-version;<![%p-not-stable;[-beta]]>-src* [.tgz or .tar.gz]
45 cd privoxy-&p-version;<![%p-not-stable;[-beta]]>
50 For retrieving the current CVS sources, you'll need CVS installed.
51 Note that sources from CVS are development quality, and may not be
52 stable, or well tested. To download CVS source:
57 cvs -d:pserver:anonymous@cvs.ijbswa.sourceforge.net:/cvsroot/ijbswa login
58 cvs -z3 -d:pserver:anonymous@cvs.ijbswa.sourceforge.net:/cvsroot/ijbswa co current
64 This will create a directory named <filename>current/</filename>, which will
65 contain the source tree.
69 Then, in either case, to build from unpacked tarball or CVS source:
76 ./configure # (--help to see options)
77 make # (the make from gnu, gmake for *BSD)
79 make -n install # (to see where all the files will go)
80 make install # (to really install)
86 The <quote>make install</quote> target is temporary quite broken! It is
87 recommended to use a binary package, or do a source build, and manually
88 install the components. Sorry.
93 If you have gnu make, you can have the first four steps
94 automatically done for you by just typing:
104 in the freshly downloaded or unpacked source directory.
108 For more detailed instructions on how to build Redhat and SuSE RPMs,
109 Windows self-extracting installers, building on platforms with
110 special requirements etc, please consult the <ulink
111 url="../developer-manual/newrelease.html">developer manual</ulink>.
114 <!-- print for README only -->
117 For binary RPM installation, and other platforms, see the user-manual