I should mention that when this was originally brought up when the
autoconf work was originally done, nobody objected. I personally hate
this solution, but I am beginning to really hate libtool and autoconf, so
I am the wrong person to talk to about this.
Ryan
On Wed, 18 Oct 2000, Greg Stein wrote:
> Yup. Way broken. I noticed this recently as I was working on mod_dav_svn.
>
> I don't have an answer yet, though :-( *sigh*
>
> Cheers,
> -g
>
> On Tue, Oct 17, 2000 at 03:02:45PM -0700, rbb@covalent.net wrote:
> >
> > The only way to do this currently, is to create a config.m4 file and put
> > your module under the modules directory. Apache will automatically detect
> > the config.m4 and it will allow you to add the module with the standard
> > --enable-module_name arguments. The config.m4 file should look like the
> > one in modules/proxy.
> >
> > I haven't been able to find a way to get autoconf to do this
> > automatically, but I haven't looked for a while.
> >
> > Ryan
> >
> > On Tue, 17 Oct 2000, Ovies Brabson wrote:
> >
> > > How does one cause Apache 2.0 to build and statically link in a 3rd
> > > party module that is made up of multiple files and for which a make file
> > > exists already? In Apache 1.3, I used to be able to use the
> > > --activate-module option of the configure script. The --with-module
> > > option of the current configure script does not seem to be what I'm
> > > looking for.
> > >
> >
> >
> > _______________________________________________________________________________
> > Ryan Bloom rbb@apache.org
> > 406 29th St.
> > San Francisco, CA 94131
> > -------------------------------------------------------------------------------
>
> --
> Greg Stein, http://www.lyra.org/
>
_______________________________________________________________________________
Ryan Bloom rbb@apache.org
406 29th St.
San Francisco, CA 94131
-------------------------------------------------------------------------------
|