+1
Guenter Knauf wrote:
Hi,
in order to simplify future configuration, and most important to have same
include path structure with both in-tree and installed compilations I think it
makes sense to move all mod_*.h headers with public APIs to the common
./include folder.
Current votes:
+1
Hi,
Please specify which headers specifically you consider to be public.
at least:
mod_cache.h
mod_core.h
mod_dav.h
mod_dbd.h
mod_proxy.h
mod_session.h
For example, are mod_ssl's headers public?
I'm not sure; mod_ssl.h and a couple of other module headers contain
APR_DECLARE_OPTIONAL_FN();
if
On 04/12/2008 12:41 AM, Guenter Knauf wrote:
Hi, in order to simplify future configuration, and most important to have same
include path structure with both
in-tree and installed compilations I think it makes sense to move all mod_*.h
headers with public APIs to the common
./include folder.
2008/4/13 Guenter Knauf [EMAIL PROTECTED]:
Hi,
Please specify which headers specifically you consider to be public.
at least:
mod_cache.h
mod_core.h
mod_dav.h
mod_dbd.h
mod_proxy.h
mod_session.h
Also:
mod_auth.h
So it doesn't get missed out of Windows installers like it has
Hi,
in order to simplify future configuration, and most important to have same
include path structure with both in-tree and installed compilations I think it
makes sense to move all mod_*.h headers with public APIs to the common
./include folder.
Current votes:
+1 wrowe, fuankg
please vote,
Guenter Knauf wrote:
in order to simplify future configuration, and most important to have same
include path structure with both in-tree and installed compilations I think it
makes sense to move all mod_*.h headers with public APIs to the common
./include folder.
Current votes:
+1 wrowe,
Guenter Knauf wrote:
in order to simplify future configuration, and most important to
have same include path structure with both in-tree and installed
compilations I think it makes sense to move all mod_*.h headers with
public APIs to the common ./include folder.
+1 since it simplifies my
