>>>As serveral other modules like mod_rewrite install their own >>>header file, I tried to integrate my module into the apache >>>build. I created my own directory under /modules, copied >>>a config.m4 and adopted it for my purpose (nothing more than a >>>APACHE_MODPATH_INIT, APACHE_MODULE and APACHE_MODPATH_FINISH). >>>For the sake of simplicity, let's assume it's just a single .c >>>and .h file with minimalistic code (I also tried this simplest >>>case). Than I ran buildconf, my module appears in configure, >>>get's built and installed - but the header file won't be >>>installed into include. I tried to mimic every step mod_rewrite >>>does (except that it's bundled with the other mapper modules), >>>but couldn't find out which step does the trick. > >I don't think there's any automatic facility provided for this. > >For example, the top-level apache Makefile knows specifically about >mod_rewrite's header file.
I was afraid of that. As I'm not that deep into autotools, I suspected that Makefile.in (I found mod_rewrite.h there) is generated somewhere else, e.g. by buildconf. >>>Btw - why are some of the .m4 files named config9.m4 or >>>config5.m4? Is this on purpose and if yes, why? > >ordering I believe This makes sense, indeed. Thanks for your reply. Looks like I have to find another way :-) Regards, Edgar
