On Wednesday 24 September 2008 06:54:50 Ralf Wildenhues wrote:
> * Bryan Bennetts wrote on Tue, Sep 23, 2008 at 05:01:21PM CEST:
> > > > If I do include the aclocal.m4, the configure *still* kicks off
> > > > automake because of a subdirs file that is created by configure being
> > > > newer than t
* Bryan Bennetts wrote on Tue, Sep 23, 2008 at 05:01:21PM CEST:
> >
> > > If I do include the aclocal.m4, the configure *still* kicks off automake
> > > because of a subdirs file that is created by configure being newer than
> > > the configure.in, which the Makefile.in is dependant on.
> >
> > Wha
On Tuesday 23 September 2008 14:45:33 Brian Dessent wrote:
> I think the real question is how are you generating this distribution
> tarball? You should be using "make dist" and it should automatically
> include all the necessary files with correct timestamps so as to not
> require any developer t
***Sent again cause this mail got bounce from the automake mailing list
presumably due to the attachment (now removed)***
On Tuesday 23 September 2008 14:45:33 Brian Dessent wrote:
> Bryan Bennetts wrote:
> > So question #1 is should aclocal.m4 be in my distribution?
>
> Strictly speaking, a user
Bryan Bennetts wrote:
> So question #1 is should aclocal.m4 be in my distribution?
Strictly speaking, a user should not even need m4 installed at all (nor
autoconf, nor automake, etc) to run the configure script and build the
software. However common courtesy dictates that you should distribute
Hi guys,
I've been redirected to you from the KDevelop forums, as they say I should be
asking you this question.
I've got a problem with a source distribution of an app I've written, when the
user runs ./configure it automatically kicks off automake cause aclocal.m4
isn't included in my dist
