diff options
author | Xavier Roche <roche@httrack.com> | 2016-08-24 10:30:22 +0200 |
---|---|---|
committer | Xavier Roche <roche@httrack.com> | 2016-08-24 10:30:22 +0200 |
commit | a9a7aa6c523001a5fbedde801a536f13c417aed6 (patch) | |
tree | ace31c65e7b815a7d288d277900f0c41b8ddf423 /INSTALL | |
parent | 96cb7434336f2bfabdf755fd14a77e0b15e6829b (diff) |
Updated version to 3.48-24
Diffstat (limited to 'INSTALL')
-rw-r--r-- | INSTALL | 21 |
1 files changed, 8 insertions, 13 deletions
@@ -50,36 +50,31 @@ of `autoconf'. The simplest way to compile this package is: - 1. From a shell command prompt, retrieve the latest source from the - git repository and sub repositories by typing: - - `git clone --recursive https://github.com/xroche/httrack.git' - - 2. `cd' to the directory containing the package's source code and type + 1. `cd' to the directory containing the package's source code and type `./configure' to configure the package for your system. Running `configure' might take a while. While running, it prints some messages telling which features it is checking for. - 3. Type `make' to compile the package. + 2. Type `make' to compile the package. - 4. Optionally, type `make check' to run any self-tests that come with + 3. Optionally, type `make check' to run any self-tests that come with the package, generally using the just-built uninstalled binaries. - 5. Type `make install' to install the programs and any data files and + 4. Type `make install' to install the programs and any data files and documentation. When installing into a prefix owned by root, it is recommended that the package be configured and built as a regular user, and only the `make install' phase executed with root privileges. - 6. Optionally, type `make installcheck' to repeat any self-tests, but + 5. Optionally, type `make installcheck' to repeat any self-tests, but this time using the binaries in their final installed location. This target does not install anything. Running this target as a regular user, particularly if the prior `make install' required root privileges, verifies that the installation completed correctly. - 7. You can remove the program binaries and object files from the + 6. You can remove the program binaries and object files from the source code directory by typing `make clean'. To also remove the files that `configure' created (so you can compile the package for a different kind of computer), type `make distclean'. There is @@ -88,12 +83,12 @@ of `autoconf'. all sorts of other programs in order to regenerate files that came with the distribution. - 8. Often, you can also type `make uninstall' to remove the installed + 7. Often, you can also type `make uninstall' to remove the installed files again. In practice, not all packages have tested that uninstallation works correctly, even though it is required by the GNU Coding Standards. - 9. Some packages, particularly those that use Automake, provide `make + 8. Some packages, particularly those that use Automake, provide `make distcheck', which can by used by developers to test that all other targets like `make install' and `make uninstall' work correctly. This target is generally not run by end users. |