On 01/09/2012 01:02 PM, Kinkie wrote:
> On Mon, Jan 9, 2012 at 8:53 PM, Alex Rousskov
> <[email protected]> wrote:
>> On 12/27/2011 05:56 AM, Kinkie wrote:
>>> Hi all,
>>> I'd like to add the attached file to the top-level squid directory.
>>> It is meant to track dependencies for regenerating the toplevel
>>> configure only when needed.
>>> The end result is a
>>> make -f Makefile.bootstrap && ./configure ; make
>>>
>>> which make bootstrapping depend on changes to the dependencies list.
>>>
>>> What do you think?
>>
>> -0: Since bootstrapping is much faster than ./configure && make, running
>>
>> ./bootstrap.sh && ./configure && make
>>
>> seems to be simpler, less error prone, almost as efficient, and does not
>> require introducing another dependency that needs to be maintained
>> (between project files and Makefile.bootstrap file).
>
> Its main purpose for me is to be used as a master build script for
> eclipse, which is quite geared towards using make as a build command
> (there's a version of the eclipse boold toolchain which understand
> autotools, but squid does quite an extensive use of magickry on top).
How about a simple Makefile like this:
all:
./bootstrap.sh && ./configure && make
This will help you in an eclipse environment without introducing a lot
of new dependencies and complexity. This simple Makefile does not even
need to be committed, I guess. You can just use it on your Eclipse
machine(s).
Alex.
