Re: Should we integrate libTrie into our build system?

Hi all,
  the attached patch removes libTrie's own autotools instrumentation,
and leverages squid's instead.
The aim is to improve portability, the nice-to-have side-effect is
cutting compile time.
(note: my test build on ubuntu roaring is currently failing due to
issues highlighted by clang's static code checker elsewhere), I'll
cover it separately.

Comments?

On Sun, Jun 9, 2013 at 11:41 PM, Robert Collins
<robertc_at_robertcollins.net> wrote:
> On 10 June 2013 08:40, Kinkie <gkinkie_at_gmail.com> wrote:
>> Hi all,
>> while attempting to increase portability to recent clang releases, I
>> noticed that libTrie hasn't benefited from the portability work that
>> was done in the past few years.
>>
>> I can see three ways to move forward:
>> 1- replicate these changes into libTrie
>> 2- change libTrie to piggyback squid's configuration variables
>> 3- fully integrate libTrie into squid's build system. Unless Robert
>> knows otherwise, squid is the only user of this library..
>
> I'm not aware fo it being shipped/used separately. Probably want to
> replace it by now, must be a tuned equivalent somewhere :)
>
> -Rob
>> Comments?
>>
>> --
>> /kinkie
>
>
>
> --
> Robert Collins <rbtcollins_at_hp.com>
> Distinguished Technologist
> HP Cloud Services

-- 
    /kinkie