./configure file in cvs

[Gioele Barabucci]

Hello everyone,

why is there a ./configure file in your cvs?
configure was meant to be created for endusers, not for developers. Many 
projects based on auto* tools create a ./autogen.sh or ./bootstrap script.
The fact is that the configure supplied (and all the auto* files) creates 
lot of confusion and some errors sometime.

simple as:

#!/bin/sh
#

rm -f configure ltmain.sh config.guess config.sub

echo "Running libtoolize..."
libtoolize --force --copy >/dev/null
echo "Running aclocal..."
aclocal $ACLOCAL_FLAGS
echo "Running autoheader..."
$use_autoheader
echo "Running autoconf..."
$use_autoconf
echo "Running automake..."
automake --add-missing --copy --foreign

[Marcus Meissner]

On Wed, Aug 29, 2001 at 02:47:48PM +0200, Gioele Barabucci wrote:
> Hello everyone,
>
> why is there a ./configure file in your cvs?
> configure was meant to be created for endusers, not for developers. Many 
> projects based on auto* tools create a ./autogen.sh or ./bootstrap script.
> The fact is that the configure supplied (and all the auto* files) creates 
> lot of confusion and some errors sometime.

It is for convienence, so not all users need to have autoconf and autoheader.

We are not using automake and libtool.

Ciao, Marcus

[Andreas Mohr]

On Wed, Aug 29, 2001 at 02:47:48PM +0200, Gioele Barabucci wrote:
> Hello everyone,
>
> why is there a ./configure file in your cvs?
> configure was meant to be created for endusers, not for developers. Many 
> projects based on auto* tools create a ./autogen.sh or ./bootstrap script.
> The fact is that the configure supplied (and all the auto* files) creates 
> lot of confusion and some errors sometime.

I'd say this is because the Wine CVS is a hybrid of developer and end user
code base.
"Normal" projects are so mature that you can easily split them into an
"end user" and a "developer" section, i.e.: deb/rpm and CVS.
Not so with Wine.

Due to the rapid development nature of the project, it's beneficial
even for end users to get latest CVS sometimes.
And end users normally don't have auto* installed, that's for sure.
(they're even struggling way too much with missing devel headers already !!)

And besides, it's mentioned in the README file like that (./configure),
so there shouldn't be *any* confusion ;-)

(yeah, RTFM still does apply, and it probably always will)