Mailing-List: contact apreq-dev-help@httpd.apache.org; run by ezmlm
Precedence: bulk
Subject: Re: Static linking of mod_apreq into Apache 2
From: Bojan Smojver <bojan@rexursive.com>
To: APREQ List <apreq-dev@httpd.apache.org>
In-Reply-To: <m34qyur0uk.fsf@sol.sunstarsys.com>
References: <1064879652.1279.2.camel@beast.rexursive.com>
	 <m34qyur0uk.fsf@sol.sunstarsys.com>
Content-Type: text/plain
Message-Id: <1064925797.9112.5.camel@furby.rexursive.com>
Mime-Version: 1.0
Date: Tue, 30 Sep 2003 22:43:18 +1000
Content-Transfer-Encoding: 7bit

It's actually not that complicated to do. In the module I'm developing
(mod_spin), which is using mod_apreq, this is already done (mostly
pinched from mod_jk). Of course, you have to "buildconf && ./config.nice
&& make && make install" Apache after you install the module, but that's
about it.

I might give it a try. It's just a matter of fiddling with configure.ac
and Makefile.am.

On Tue, 2003-09-30 at 21:07, Joe Schaefer wrote:
> Bojan Smojver <bojan@rexursive.com> writes:
> 
> > Is that currently possible? I haven't noticed those options in
> > configure/build process...
> 
> I don't think so- wouldn't that require mod_apreq to be 
> compiled *before* httpd?  Our current build system assumes 
> httpd is already installed, so I guess you'd need to figure
> out how to configure libapreq/mod_apreq from the httpd-2.0 
> source, plus tell httpd to build and link it in during *its* 
> compile.
> 
> That would be a nice feature to have, but I don't think anyone
> has volunteered to do it.
-- 
Bojan