X-Git-Url: http://www.privoxy.org/gitweb/?p=privoxy.git;a=blobdiff_plain;f=doc%2Fsource%2Fbuildsource.sgml;h=963760a60f8ed0931eb5a3ecfcaa68533a2340bf;hp=bc439bacf7a6b37d4e4c765d1c0fc93b02e88ab6;hb=72081f829de368392d04076728f8c991178c0080;hpb=d7cc11956d778be9da159f012e80733d2d082706 diff --git a/doc/source/buildsource.sgml b/doc/source/buildsource.sgml index bc439bac..963760a6 100644 --- a/doc/source/buildsource.sgml +++ b/doc/source/buildsource.sgml @@ -3,43 +3,52 @@ Purpose : Entity included in other project documents. - $Id: buildsource.sgml,v 1.0 2002/04/04 01:14:18 hal9 Exp $ - - Written by and Copyright (C) 2001 the SourceForge - Privoxy team. http://www.privoxy.org/ - - Based on the Internet Junkbuster originally written - by and Copyright (C) 1997 Anonymous Coders and - Junkbusters Corporation. http://www.junkbusters.com + $Id: buildsource.sgml,v 1.9.2.3 2003/11/06 13:36:37 oes Exp $ + Copyright (C) 2001, 2002 Privoxy Developers + See LICENSE. ====================================================================== This file used for inclusion with other documents only. ====================================================================== + If you make changes to this file, please verify the finished + docs all display as intended. + + This file is included into: + + user-manual + README + --> + - There are several ways to install Privoxy. + To build Privoxy from source, + autoconf, + GNU make + (gmake), and, of course, a C compiler like gcc are required. - To build Privoxy 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: tar xzvf privoxy-&p-version;-src* [.tgz or .tar.gz] cd privoxy-&p-version; - + - - 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: @@ -47,7 +56,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 - + @@ -63,24 +72,37 @@ 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) - + make -n install # (to see where all the files will go) + make install # (to really install) + + + + + If you have gnu make, you can have the first four steps + automatically done for you by just typing: + + + + + make + + + + + in the freshly downloaded or unpacked source directory. - Redhat and SuSE src and binary RPMs can be built with - make redhat-dist or - make suse-dist from unpacked sources. You - will need to run autoconf; autoheader; - ./configure beforehand. *BSD will require gmake (from - http://gnu.org). - + 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 developer manual. + For binary RPM installation, and other platforms, see the user-manual