Ok. ( plus ant )
of course ;)
But I'm not sure I understand why do we need automake - if autoconf
can generate only the build.properties file ( and probably a .h ).
I think automake was used to generate the stuff for static build
but I removed now.
The makefile and ant should read the
On Tue, 14 May 2002, GOMEZ Henri wrote:
The makefile and ant should read the build.properties to get settings
to use ( and that will also allow manual config ).
Do you agree having build.properties generated by autoconf ?
+1.
I don't mind if it also tries to 'guess' locations for the
Do you agree having build.properties generated by autoconf ?
+1.
ok
I don't mind if it also tries to 'guess' locations for the
other packages
we use ( like looking in /usr/share/java ).
hum, the autoconf is for now limited to native code
generation.
Is it possible to generate
GOMEZ Henri wrote:
jakarta-tomcat-connectors/jk/native2/server/apache2/Makefile
Index: Makefile
===
RCS file:
/home/cvs/jakarta-tomcat-connectors/jk/native2/server/apache2/M
akefile,v
retrieving revision 1.4
retrieving
On Mon, 13 May 2002, GOMEZ Henri wrote:
We've got a problem here with all the automake stuff added.
There is allready a Makefile.in which will scratch your Makefile
after autoconf
BTW, you're current Makefile seems ready for autoconf/m4 processing
APACHE2_HOME, and the
