On Mon, Dec 18, 2017 at 7:34 AM, mika ristimaki <[email protected]> wrote: > Hi all,
Hello Mika! > I noticed that the source code distributions > (http://www.squid-cache.org/Versions/v4/) and the repository > (https://github.com/squid-cache/squid) differ in a sense that the tar.gz > packages include the configure script and Makefiles. > > > I am trying to replicate it, and I it looks to me that the configure > scripts, etc., are created by running ./bootstrap.sh. But looking at the > bootstrap.sh it has this > > > # On MAC OS X, GNU libtool is named 'glibtool': > > if [ `uname -s 2>/dev/null` = 'Darwin' ] > > then > > LIBTOOL_BIN="glibtool" > > else > > LIBTOOL_BIN="libtool” > > fi > > > So it is platform dependant. Yes. > So my question is how platform independent configure scripts are created if > bootstrap.sh is platform dependant? Or what I am missing here? Exactly through bootstrap.sh :) The full build process for Squid-from-source is $ bootstrap.sh && ./configure && make This is because bootstrap builds auto-generated code (e.g. configure) which makes no sense to have in our source repository. At the same time, building from source requires additional tools (e.g. autoconf, automake, libtoolize) which may not be present on an user's build system, so these generated bits are included in the distribution tarball. -- Francesco _______________________________________________ squid-dev mailing list [email protected] http://lists.squid-cache.org/listinfo/squid-dev
