IMHO, ant should not be used to generate the configure and makefile scripts;
Instead the building process must avoid all these specific Unix tools
like autoconf/configure. As a example of a great usage of ant for building a
product, have a look to the directory in the Apache axis project :
ws-axis/c/build.
It is the build directory for the Apache Axis C version targeting the
major platforms as Linux, OS/400 HP-UX, OS/390 and so on.
I am using a similar approach for a tool targeting WXP, Linux, OS/390 and it
works as expected: only one build infrastructure for all platforms.
Regards
Francis
----- Original Message -----
From: "Graham Leggett" <[EMAIL PROTECTED]>
To: <[email protected]>
Sent: Thursday, December 08, 2005 3:28 PM
Subject: Re: Directions for Win32 binary httpd
Francis ANDRE wrote:
I do not address APR, but httpd. So even if APR seems to need make (while
I am not really convince that ant cannot makes the job)., ant could be
use for the httpd build process.
The biggest body of work that needs to be done during the build is handled
in the ./configure script. The ./configure script (built by autoconf) is
designed already to handle the different types of make out there.
Changing from make to ant would involve teaching autoconf to create
./configure to make ant scripts instead of Makefiles, and that's just
doing the same thing just using a different program, it buys nothing.
If however you extended ant so that it could do the job of
autoconf/configure, then you would be onto something. But only on
platforms that supported Java, of course.
Regards,
Graham
--
