3 To reduce bandwidth and needless updates, the CVS tree does not
4 contain automatically generated files, even when those are normally
5 present in the distribution tarballs. All of these are recreated by
6 the build process, except for `configure', which is needed to start
7 the build in the first place.
9 To build Wget from the CVS sources, all you need aside from the normal
10 C development tools (make, cc) is Autoconf, which you can get from
11 <http://www.gnu.org/software/autoconf/autoconf.html>. Wget does not
12 use Automake or Libtool, so you needn't worry about those.
14 For your convenience, Makefile.cvs is a make file containing the
15 necessary preparations, which currently amount to calling Autoconf.
16 Invoke it with `make -f Makefile.cvs', and after that you're ready to
17 build Wget in the normal fashion, e.g. with `./configure' followed by
20 The simplest example of downloading and building Wget from CVS can
23 cvs -d :pserver:... checkout wget
30 The instructions that explain how to check out Wget from CVS in the
31 first place are available at <http://sunsite.dk/wget/> under