moparisthebest/wget
1
0
Fork 0
mirror of https://github.com/moparisthebest/wget synced 2024-07-03 16:38:41 -04:00
Code Issues Releases Wiki Activity

[svn] README.cvs: Falsely claimed you only needed GNU autoconf to build from the CVS

Browse Source 
sources.  You also need GNU gettext and texinfo.  I also did a bunch of general
re-writing of this file.
This commit is contained in:
dan 2001-01-06 02:15:58 -08:00
parent cbe2ca1b80
commit 2204604381
2 changed files with 23 additions and 21 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
ChangeLog
View File

@ -7,6 +7,10 @@
* README.branches: Explains the 1.6_branch.ChangeLog files.
* README.cvs: Falsely claimed you only needed GNU autoconf to
build from the CVS sources. You also need GNU gettext and
texinfo. I also did a bunch of general re-writing of this file.
2001-01-03 Dan Harkless <wget@harkless.org>
* TODO: We should make a simple man page referring to info doco.
@ -47,6 +51,8 @@
* windows/Makefile.in: New file.
* README.cvs: New file.
2000-11-25 Karl Eichwalder <ke@suse.de>
* Makefile.in (SUBDIRS): Add 'windows'.

38
README.cvs
View File

@ -1,32 +1,28 @@
Important note:
To reduce bandwidth and needless updates, the CVS tree does not
contain automatically generated files, even when those are normally
present in the distribution tarballs. All of these are recreated by
the build process, except for `configure', which is needed to start
the build in the first place.
contain automatically-generated files, even when those files are
normally present in the distribution tarballs.
To build Wget from the CVS sources, all you need aside from the normal
C development tools (make, cc) is Autoconf, which you can get from
<http://www.gnu.org/software/autoconf/autoconf.html>. Wget does not
use Automake or Libtool, so you needn't worry about those.
Therefore, if you're building from the CVS sources, you'll need to
have GNU autoconf, gettext, and texinfo installed on your machine
(these do the afore-mentioned automatic generation). The three
packages are available from <ftp://ftp.gnu.org/pub/gnu/<package>/> and
its mirrors (please choose one close to you), listed at
<http://www.gnu.org/order/ftp.html>.
For your convenience, Makefile.cvs is a make file containing the
necessary preparations, which currently amount to calling Autoconf.
Invoke it with `make -f Makefile.cvs', and after that you're ready to
build Wget in the normal fashion, e.g. with `./configure' followed by
`make'.
In case you aren't used to running autoconf manually to generate the
necessary configure script, a file called Makefile.cvs has been
provided, and may be called using `make -f Makefile.cvs'. Once the
Makefile has called autoconf to generate the configure script, you can
build in the usual fashion.
The simplest example of downloading and building Wget from CVS can
look like this:
To summarize, once you've checked out wget from the CVS archive
(instructions for which can be found on the Development page of the
Wget website), the commands you'll execute will be as follows (barring
any extra options to `configure' or to the second `make'):
cvs -d :pserver:... checkout wget
cd wget
make -f Makefile.cvs
./configure
make
The instructions that explain how to check out Wget from CVS in the
first place are available at <http://sunsite.dk/wget/> under
"Development".