Re: Current status of third-party module procedures?

[ra...@bellglobal.com]

> In 1.3, you can use a module-definition section in mod_php.c to alter the
> CFLAGS and LIBS settings.  See something like mod_auth_dbm for an example.
> You should be able to fiddle WANTHSREGEX in the same way.  mod_php.[ch]
> should probably go into a seperate directory.  You could consider doing
> the whole PHP build in something like src/modules/extra/php.

Sorry for being dense here, but I don't see the code you are referring to
in mod_auth_dbm.  I am looking at a CVS update from today of 1.3a2-dev.

The ideal solution for me would be if I could create a mod_php.def file or
something like that and then  when the user runs Configure it would go and
read all the various *.def files are create INCLUDES, CFLAGS, LIBS and also
override WANTHSREGEX or any other Configure settings.

-Rasmus

Re: Current status of third-party module procedures?

[ra...@bellglobal.com]

> See also src/modules/standard/mod_auth_db.module

Ah, sorry guys.  I did a checkout on "apache" instead of "apachen".

-Rasmus

Re: Current status of third-party module procedures?

[Dean Gaudet <dg...@arctic.org>]

See also src/modules/standard/mod_auth_db.module

Dean

On Tue, 2 Sep 1997 rasmus@bellglobal.com wrote:

> > In 1.3, you can use a module-definition section in mod_php.c to alter the
> > CFLAGS and LIBS settings.  See something like mod_auth_dbm for an example.
> > You should be able to fiddle WANTHSREGEX in the same way.  mod_php.[ch]
> > should probably go into a seperate directory.  You could consider doing
> > the whole PHP build in something like src/modules/extra/php.
> 
> Sorry for being dense here, but I don't see the code you are referring to
> in mod_auth_dbm.  I am looking at a CVS update from today of 1.3a2-dev.
> 
> The ideal solution for me would be if I could create a mod_php.def file or
> something like that and then  when the user runs Configure it would go and
> read all the various *.def files are create INCLUDES, CFLAGS, LIBS and also
> override WANTHSREGEX or any other Configure settings.
> 
> -Rasmus
> 
> 

Re: Current status of third-party module procedures?

[Marc Slemko <ma...@worldgate.com>]

On Tue, 2 Sep 1997 rasmus@bellglobal.com wrote:

> > In 1.3, you can use a module-definition section in mod_php.c to alter the
> > CFLAGS and LIBS settings.  See something like mod_auth_dbm for an example.
> > You should be able to fiddle WANTHSREGEX in the same way.  mod_php.[ch]
> > should probably go into a seperate directory.  You could consider doing
> > the whole PHP build in something like src/modules/extra/php.
> 
> Sorry for being dense here, but I don't see the code you are referring to
> in mod_auth_dbm.  I am looking at a CVS update from today of 1.3a2-dev.

The section starting MODULE-DEFINITION-START and ending
MODULE-DEFINITION-END will be run by Configure.

Re: Current status of third-party module procedures?

[Paul Sutton <pa...@ukweb.com>]

On Tue, 2 Sep 1997 rasmus@bellglobal.com wrote:
> The ideal solution for me would be if I could create a mod_php.def file or
> something like that and then  when the user runs Configure it would go and
> read all the various *.def files are create INCLUDES, CFLAGS, LIBS and also
> override WANTHSREGEX or any other Configure settings.

If you haven't seen it already, you might to have a look at
htdocs/manual/sourcereorg.html (in apachen). It includes some basic
information for module authors about how to use these new features, plus
references to the examples in mod_auth_db{m}.(c|module). The docs are
pretty basic so feedback on how to make them more useful to third-party
module authors would be appreciated...

And yes, you can create a definition file (mod_php.module) which includes
anything you need Configure to know about when it runs. 

Another module to look at is mod_status which shows how to use the current
value of a Rule from Configure to alter the cflags. 

//pcs