Apache 2.0 - the right way to statically link third party modules?

["Gregory (Grisha) Trubetskoy" <gr...@ispol.com>]

Could someone please give me a clue on where to look for information on
statically linking third party modules in Apache 2.0?

The --with-module option seems to expect there to be a *.c file under
modules subdirectory. But if the module has multiple *.c files and
requires additional includes and a library - what is the best way to
handle it?

In Apache 1.3 one could create a lib (using ar/ranlib), then copy it into
the Apache source tree under modules, drop a Makefile.libdir,
Makefile.tmpl and a libxxx.module file there. What is the equivalent of
doing this in Apache 2.0, if any?



P.S. Whatever happened to the apache-modules list?
http://httpd.apache.org/lists.html lists it as
apache-modules@covalent.net, but that doesn't work.

Thanks,

Grisha

Re: Apache 2.0 - the right way to statically link third party modules?

[Aaron Bannert <aa...@clove.org>]

On Fri, Jun 21, 2002 at 12:07:23PM -0400, Gregory (Grisha) Trubetskoy wrote:
> P.S. Whatever happened to the apache-modules list?
> http://httpd.apache.org/lists.html lists it as
> apache-modules@covalent.net, but that doesn't work.

Works fine for me. Send a message to
apache-modules-subscribe@covalent.net

-aaron