Re: Squid sub-libs

On Sat, 2008-03-08 at 18:55 +1300, Amos Jeffries wrote:
> Alex Rousskov wrote:
> > On Sat, 2008-03-08 at 10:52 +1300, Amos Jeffries wrote:
> >> In line with the 3.1 cleanup and re-arranging I'd like to propose a
> >> change to the naming scheme of the *.la files squid produces.
> >>
> >> Namely that they get called libsquid-X.la instead of just libX.la.
> >>
> >> This would mean:
> >> libsquid-auth.la, libsquid-fs.la, libsquid-icap.la, libsquid-esi.la,
> >> libsquid-acl.la, etc
> >>
> >> That will reduce some makefile confusion between external libraries and
> >> ones built into squid. Case in point: we already have two libmisc.* linked.
> >>
> >> Input?
> >
> > I think we should link with group/libgroup.la libraries and compile with
> > group/name.h headers rather than adding Squid prefixes everywhere. If we
> > want Squid prefix as an extra protection, we could use
> > squid/group/name.*
>
> What happens then after you decide to publish the group headers for eCAP?
> People linking against libgroup.l.so as they need? or one monolithic
> libsquid.l.so with all squid headers needed by the smallest client app?

I hope eCAP does not require publishing Squid headers, but if folks need
to link with published Squid libraries or use headers (if any and for
whatever reason), they would #include group/name.h and link with
group/name.so (or squid/group/name.*).

Alex.
Received on Fri Mar 07 2008 - 23:18:13 MST