On Tue, Nov 03, 1998, Martin Maciaszek wrote:
> So far mod_ssl can only be built with apache sources. I've tanken a look at
> mod_php3 and it can be built without the apache sources (just the header
> files).
<grin> Yes, I know, because I was the guy who initially implemented this
APXS-based approach for PHP3 (and APXS itself ;-).
> Is there any way to build mod_ssl as a module without having the
> apache sources. I think it would be very useful when building RPMs.
Sure, theoretically you can build mod_ssl via APXS, too. But it will not run
with a standard Apache, because you need the Extended API (EAPI) I've recently
wrote for Apache. But you can do the following: Create package of Apache+EAPI
(by just applying mod_ssl to the sources of Apache but then instead of
--enable-module=ssl you use just --enable-rule=EAPI) and then you built a
standalone package for mod_ssl itself (for the libssl.so to be correct).
> I think in mod_php3 they use something called apaci (I'm not familiar with
> this).
APACI is the Apache Autoconf-style Interface I've written for Apache 1.3.
What you mean is actually APXS: the APache eXtenSion tool.
> Is anything similar planned for mod_ssl? I'd love just to install
> mod_ssl to my existing apache installation, and not installing a complete
> new apache. Are there any cons against this approach?
The idea itself is fine. But remember that EAPI is still not part of Apache
1.3. So you _CANNOT_ expect to built a standard Apache and use it with
mod_ssl. This doesn't work. So, in short: you _have_ to build at least
Apache+EAPI.
Ralf S. Engelschall
[EMAIL PROTECTED]
www.engelschall.com
______________________________________________________________________
Apache Interface to SSLeay (mod_ssl) www.engelschall.com/sw/mod_ssl/
Official Support Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
