Michaël CATANZARITI wrote:
ok for the patch !
Unfortunately it does not work as expected. I cannot generate a
config_unix.h file from config_unix.h.in the same way config_auto.h was
generated from config_auto.h.in.
So I had a look to autoconf and how to optionally install headers. It's
quite s
ok for the patch !
Christophe de VIENNE wrote:
Hi,
I've been thinking about the macro definitions problem.
I think I've found a more simple solution than what we discussed
previously.
The idea would be to keep a config_auto.h.in file, but hand-written,
with only the macros that are necessary to
Hi,
I've been thinking about the macro definitions problem.
I think I've found a more simple solution than what we discussed previously.
The idea would be to keep a config_auto.h.in file, but hand-written,
with only the macros that are necessary to have the header compile
correctly, and another f
mcatan 2004/06/29 06:45:45
Removed: include/log4cxx config_auto.h.in
Log:
removed generated file
Hi,
I noticed that config_auto.h.in is included in the CVS. I thinks it's
not necessary since it's generated by
AM_CONFIG_HEADER(include/log4cxx/config_auto.h) in configure.in.
A+
Christophe
[EMAIL PROTECTED] wrote:
mcatan 2004/06/29 06:09:17
Modified:.Makefile.am
Log:
added configuration scripts to distribution
Great !
Thanks,
Christophe
mcatan 2004/06/29 06:09:17
Modified:.Makefile.am
Log:
added configuration scripts to distribution
Revision ChangesPath
1.8 +2 -17 logging-log4cxx/Makefile.am
Index: Makefile.am
===
Note: I've posted this message on log4cxx-user but I guess it's place is
here...
Hi,
The build process currently impose to run 'autogen.sh' before running
configure. Although it's a good thing for a programmer using the CVS
version, I think it shouldn't be the case when compiling from the tarball
