On Jan 24, 2008 11:34 AM, Ralf Wildenhues <[EMAIL PROTECTED]> wrote:
> Hello Paulo,
>
> * Paulo J. Matos wrote on Thu, Jan 24, 2008 at 11:55:21AM CET:
> >
> > Which files of a autotools project should be kept in a control
> > versioning system?
>
> Some data (I'll let others make suggestions):
>
On Jan 24, 2008 2:59 PM, Bob Friesenhahn <[EMAIL PROTECTED]> wrote:
> On Thu, 24 Jan 2008, Ralf Wildenhues wrote:
> >> I've been keeping the files kept by make maintainer-clean but that
> >> keeps the configure script, for example, which is machine dependent (I
> >> think) , so I guess I need somet
On Jan 24, 2008 9:54 PM, Warren Young <[EMAIL PROTECTED]> wrote:
> Paulo J. Matos wrote:
> >
> > Which files of a autotools project should be kept in a control
> > versioning system?
>
> IMHO, nothing generated goes in the repository. Ever. If that means
> some developers are using different tool
Does automake allowing doing something like:
make -j5 install ?
I ask because executing /usr/bin/install for several thousand files is
incredibly slow (it takes longer to install than to build each of
these files). Running several in parallel may make it go faster, as
there's a lot of IO and ve
Couldnt it be that some option maybe added to the configure/environment variable
that it could detect autoconf from the build area, too. That way we could have
a linear build invocation where autoconf is built first (not yet installed) and
then
automake maybe equally happy ?
I think this should b