6 To build and install GNU Wget, you need to unpack the archive (which
7 you have presumably done, since you are reading this), and read on.
8 Like most GNU utilities, Wget uses the GNU Autoconf mechanism for
9 build and installation; those of you familiar with compiling GNU
10 software will feel at home.
14 To configure Wget, run the configure script provided with the
15 distribution. You may use all the standard arguments configure
16 scripts take. The most important ones are:
18 --help print help message
20 --prefix=PREFIX install architecture-independent files in PREFIX
21 (/usr/local by default)
22 --bindir=DIR user executables in DIR (PREFIX/bin)
23 --infodir=DIR info documentation in DIR [PREFIX/info]
24 --mandir=DIR man documentation in DIR [PREFIX/man]
26 --build=BUILD configure for building on BUILD [BUILD=HOST]
27 --host=HOST configure for HOST [guessed]
28 --target=TARGET configure for TARGET [TARGET=HOST]
30 --enable and --with options recognized (mostly Wget-specific):
31 --with-socks use the socks library
32 --disable-opie disable support for opie or s/key FTP login
33 --disable-digest disable support for HTTP digest authorization
34 --disable-debug disable support for debugging output
35 --disable-nls do not use Native Language Support
37 So, if you want to configure Wget for installation in your home
38 directory, you can type:
39 ./configure --prefix=$HOME
41 You can customize many default settings by editing Makefile and
42 config.h. The program will work very well without your touching these
43 files, but it is useful to have a look at things you can change there.
45 If you use socks, it is useful to add -L/usr/local/lib (or wherever
46 the socks library is installed) to LDFLAGS in Makefile.
48 To configure Wget on Windows, run configure.bat and follow the
49 instructions in the windows/ directory. If this doesn't work for any
50 reason, talk to the Windows developers listed in `windows/README'; I
51 do not maintain the port.
55 To compile the program, type make and cross your fingers. If you do
56 not have an ANSI compiler, Wget will try to KNR-ize its sources "on
57 the fly". This should make GNU Wget compilable virtually anywhere.
59 After the compilation a ready to use `wget' executable should reside
60 in the src directory. I do not have any kind of test-suite as of this
61 moment, but it should be easy enough to test whether the basic stuff
66 Use `make install' to install GNU Wget to directories specified to
67 configure (/usr/local/* by default).
69 The standard installation process will copy the wget binary to
70 /usr/local/bin, install the info pages (wget.info*) to
71 /usr/local/info. You can customize the directories either through the
72 configuration process or making the necessary changes in the Makefile.
74 To delete the files created by Wget installation, you can use make