[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: [PATCH] shared-only build for libsvn_auth_ and apache modules

From: Philip Martin <philip_at_codematters.co.uk>
Date: Thu, 20 Jul 2017 16:32:00 +0100

Greg Stein <gstein_at_gmail.com> writes:

> On Wed, Jul 19, 2017 at 5:16 PM, Philip Martin <philip_at_codematters.co.uk>
> wrote:
>
>> The way to do this is to pass the libtool argument -shared to the
>> compile and link commands. If we do this for the libsvn_auth_ libraries
>
> I can see this, in order to avoid hauling in large parts of Gnome/KDE.

The Gnome/KDE dependencies are already isolated to the auth providers,
my patch doesn't change that. All my patch does is drop the static
versions of the providers.

>> then we should probably do it for the apache modules as well. I don't
>>
>
> But Apache httpd can be built as a static build, including all modules
> statically. httpd has various logic to determine whether a module has been
> linked or must be loaded.
>
> I'm not sure how many people choose to do static linking of httpd today,
> but it is a definite removal of a feature.

Apache has support for static linking of in-tree modules but I see no
support for static linking of out-of-tree modules like Subversion. How
would it work? It's not enough to simply link a static Subversion
module -- the core httpd code would also need some Subversion specific
changes to trigger the module. I suspect that nobody does this.

-- 
Philip
Received on 2017-07-20 17:32:07 CEST

This is an archived mail posted to the Subversion Dev mailing list.