(autoconf 2.63, automake 1.11)
Why is AS found with AM_PROG_AS instead of AC_PROG_AS? Why is this an
automake thing and not an autoconf thing?
Hi Bob and Roger,
Bob Friesenhahn wrote:
I have not verified if referencing a file outside of the source tree
really works properly.
My experience is that inclusion of an external file will be ignored by
Automake, in other words, the include statement ends up in the Makefile.
It might still
On Sat, 15 Aug 2009, Roger Leigh wrote:
I hadn't come across this before; I didn't realise it had Makefile.am
fragments as well. That's perfectly OK by me.
How does one extract these bits into a project's Makefile.am
automatically? Or is it just a matter of copying and pasting the
needed bits
On Sat, 15 Aug 2009, Roger Leigh wrote:
The "release tarball" step is always needed since software
development is protected by copyright laws so we need a step which
is a equivalent to publishing the work. A release branch or tag in
a live repository will not be compelling enough in a court of
Hello again,
Following the earlier thread a few months back
("RFE: allow for computed version number"), I was looking for a
solution to this problem at the time, and implemented a scheme
similar to that proposed. In case it's useful for anyone else, I'll
detail what I'm doing below.
I use git, a
On Fri, Aug 14, 2009 at 07:53:46PM +0200, Ralf Wildenhues wrote:
> Hello Roger,
>
> * Roger Leigh wrote on Fri, Aug 14, 2009 at 11:40:18AM CEST:
> >
> > An initial implementation follows. This works, but it does need
> > further refinement (error checking, for example). And probably
> > review
* Roger Leigh wrote on Sat, Aug 15, 2009 at 12:13:21PM CEST:
> Additionally, VCSes don't typically store the results of "make dist",
> only the source for that. Due to changing tool versions over the
> years, you can get in a situation where you can no longer rebootstrap
> checkouts of old version
On Fri, Aug 14, 2009 at 09:46:52AM -0500, Bob Friesenhahn wrote:
> On Fri, 14 Aug 2009, Roger Leigh wrote:
>
> >ÿÿ distribute generated release tarball
> >
> >However, the "distribute release tarball" step is becoming less and
> >less relevant with the advent of git.
>
> The "release tarball" ste
