> > >
> > > Since apache doesn't need to be recompiled for loading the mod_dtcl as
a
> > > shared module, why don't we include the apache header in the mod_dtcl
> >tree?
> > > Then, a user won't need the apache src for adding dtcl to his server..
> > >
> >
> >Pardon me if I am totally incorrect, but I don't think it is just one
> >header. That is one header that sucks in a bunch of other headers, with
> >several platform specific header files (os.h) also being required. And
how
> >do we keep those headers in sync with changes in the Apache sources ?
>
> Of course, the Apache headers would be contained in its own dir (and
subdirs)
> And what is the problem in synching with changes in the Apache sources?
> They actually don't
> release a new version each day.. so just cp -a src/include...
>
Problem comes in for users who want to build Apache + some module that makes
changes to those header files. An example would be mod_ssl. My concern was
that our "virgin" header files would cause problems. But I think you
address this below...
> >And, speaking for the Windows minority, we need the Apache sources around
in
> >any case, in order to make a usable link library.
>
> I have no idea about this
I do since I did the build and wrote the readme :) The sources + objects
from a Win32 build of Apache are used to make a libapachecore.a that the
mod_dtcl.so (or ApacheModuleDtcl.dll) is linked against. Still a shared
module, just need to create that import lib for Win32 users.
> The configure script will accept the includes' dir in the command line,
and
> if not provided will
> use his own ones.
Great.
--Craig
Craig Huckabee [EMAIL PROTECTED]
Compliance Corporation
SPAWAR Systems Center-Charleston, SC
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
