httpd-apreq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Joe Schaefer <joe+gm...@sunstarsys.com>
Subject Re: [PATCH]: Enable static build of APREQ 2
Date Mon, 06 Oct 2003 01:47:24 GMT
Bojan Smojver <bojan@rexursive.com> writes:

[...]

> To use this feature, one would configure libapreq2 like this:
> 
> ./configure --with-apache2=/path/to/apache2/source/directory
> [--disable-shared] 
> make
> make install
> 
> The, from Apache 2 source tree, one would run:
> 
> ./buildconf
> ./config.nice
> make
> make install
> 
> After that, mod_apreq should automagically appear in the list of
> modules that are statically linked into Apache 2. You *HAVE TO*
> configure, make and make install vanilla Apache2 for this to work,
> of course. 

Looks great so far!  I haven't tried running it yet, but I'm wondering
about the apxs dependence in the patch.  Doesn't apxs depend on mod_so
being installed?  Does the preinstalled httpd need to have a working apxs?  
If not, where should/does libapreq.so wind up after installation?

Also, since we can get the apache srcdir from `apxs -q abs_srcdir`, if
we're going to require a working apxs, maybe we should just do something
with "--with-apache2-apxs=... --disable-shared" instead of adding
another configure option (and distinguish between shared/static libapreq
and shared/static mod_apreq).

Another possibility is to do something clever with httpd's 
--with-module=... option, but I'm not smart enough to get a full
compile out of it.  Maybe a small step in this direction would 
be to move httpd-apreq-2/src/* over to httpd-2.0/srclib/apreq
and figure out how to get *that* to compile libapreq.


If I'm jumping the gun by asking such questions before trying the
patch, just holler.

-- 
Joe Schaefer


Mime
View raw message