Files
httrack/INSTALL.Linux
Xavier Roche d90f3e356d build: stop tracking generated autotools files; add bootstrap/build.sh
The generated build system (configure, every Makefile.in, config.h.in,
ltmain.sh, config.guess/sub, the aux scripts) was committed so a bare git
clone could build without autotools. Nothing downstream relied on the
committed copies: CI runs autoreconf -fi, Debian regenerates via
dh_autoreconf, and the release tarball is built by make dist, which
regenerates them regardless. The only cost was a recurring footgun: a stale
Makefile.in after a *_SOURCES edit silently broke the plain build (undefined
reference to cache_selftests), and CI could not catch it.

Treat them as build products. They are now .gitignored and regenerated from
configure.ac/Makefile.am by the new ./bootstrap (autoreconf -fi), and shipped
only inside make dist tarballs so tarball users still need no autotools.
build.sh is a one-shot wrapper (bootstrap + configure + make) that runs
configure via /bin/sh, so it survives a noexec source tree. Both scripts join
EXTRA_DIST. INSTALL.Linux, README.md and AGENTS.md document the git flow:
./bootstrap before ./configure, autotools required for a git build.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Signed-off-by: Xavier Roche <roche@httrack.com>
2026-06-16 22:48:04 +02:00

22 lines
685 B
Plaintext

HTTrack Website Copier - Install notes
--------------------------------------
On most systems (including GNU/Linux), installing can be easily achieved using the following command:
./configure && make && make install
-or- (if not compiling as root)
./configure --prefix=$HOME && make && make install
Building from a git checkout (not a release tarball) first needs the build
system regenerated, which requires autoconf, automake and libtool:
./bootstrap
./configure && make && make install
You can also use the one-shot wrapper, which runs bootstrap, configure and make
(extra arguments are passed to configure):
./build.sh --prefix=$HOME
See also the INSTALL generic help file.