Re: building helpers external to squid sources

From: Eliezer Croitoru <eliezer_at_ngtech.co.il>
Date: Sun, 05 May 2013 06:12:42 +0300

On 5/3/2013 11:49 PM, Kinkie wrote:
> On Fri, May 3, 2013 at 9:06 PM, Chris Ross <cross_at_markmonitor.com> wrote:
>>
>> I've been working on a couple of helpers for our internal use. So far, I've been trying to mirror the [build] structure of the shipped helpers, and this works fine, if I copy them into the squid sources and patch the Makefile.am/in. But, I was wondering if there is a method someone else has used to build helpers for squid without having to co-locate the source. I want to be able to easily track updates to squid from the core distribution, so I don't want to co-locate our internal helpers. I can copy them into the tree and patch, as noted, but I wondered if someone else had come up with a better way.
>
> Hi Chris,
> my first thought is, what benefit do these helpers have from being
> built in the squid sources? After all helpers are just external
> programs, as long as they respect the (stdin/out) squid APIs, they
> will just work(tm). In other words, I can see no real advantage from
> building them together with squid.
>
>
> --
> /kinkie
>
unless they rely on squid code? maybe?
Never tried that one.

Eliezer
Received on Sun May 05 2013 - 03:13:01 MDT

This archive was generated by hypermail 2.2.0 : Sun May 05 2013 - 12:00:05 MDT