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 --with-ssl use the openssl library
33 --disable-opie disable support for opie or s/key FTP login
34 --disable-digest disable support for HTTP digest authorization
35 --disable-debug disable support for debugging output
36 --disable-nls do not use Native Language Support
38 So, if you want to configure Wget for installation in your home
39 directory, you can type:
40 ./configure --prefix=$HOME
42 You can customize many default settings by editing Makefile and
43 config.h. The program will work very well without your touching these
44 files, but it is useful to have a look at things you can change there.
46 If you use socks, it is useful to add -L/usr/local/lib (or wherever
47 the socks library is installed) to LDFLAGS in Makefile.
49 To configure Wget on Windows, run configure.bat and follow the
50 instructions in the windows/ directory. If this doesn't work for any
51 reason, talk to the Windows developers listed in `windows/README'; I
52 do not maintain the port.
56 To compile the program, type make and cross your fingers. If you do
57 not have an ANSI compiler, Wget will try to KNR-ize its sources "on
58 the fly". This should make GNU Wget compilable virtually anywhere.
60 After the compilation a ready to use `wget' executable should reside
61 in the src directory. I do not have any kind of test-suite as of this
62 moment, but it should be easy enough to test whether the basic stuff
67 Use `make install' to install GNU Wget to directories specified to
68 configure (/usr/local/* by default).
70 The standard installation process will copy the wget binary to
71 /usr/local/bin, install the info pages (wget.info*) to
72 /usr/local/info. You can customize the directories either through the
73 configuration process or making the necessary changes in the Makefile.
75 To delete the files created by Wget installation, you can use make