[squid-dev] Compiling from repository checkout

[mika ristimaki]

On 18 Dec 2017, 10.44 +0200, Kinkie <gkinkie at gmail.com>, wrote:
> On Mon, Dec 18, 2017 at 7:34 AM, mika ristimaki
> <mika.ristimaki at gmail.com> wrote:
>
> > 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.


Thanks, got it. One more question. Do you know why bootstrap.sh verifies that glibtool is installed in OS X. Cause I tried this

brew install libtool
./bootstrap.sh
brew uninstall libtool
./configure && make

And squid builds (and runs) just fine. But If I do

brew uninstall libtool
./bootstrap.sh

Then bootstrapping fails saying glibtool is not installed.

The reason I am asking is that if I don’t uninstall glibtool, the final binary will have dependency to dynamic glibtool lib.  The glibtool is installed to Homebrew default path (/usr/local/..) and doesn’t necessarily exists in other OS X installations. So if I want to give the binary I build to my coworker it may not work in his machine unless he installs glibtool first through homebrew.

-Mika

>
>
> --
> Francesco
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.squid-cache.org/pipermail/squid-dev/attachments/20171218/f1aefd2c/attachment.html>