Re: Help2man and Parallel Make Race

2012-11-19 Thread Neil T . Dantam
Thank you for the thoughtful response, Stefano. At Mon, 19 Nov 2012 22:53:07 +0100, Stefano Lattarini wrote: > On 11/19/2012 08:55 PM, Neil T. Dantam wrote: > > > > * Don't distribute prebuilt manpages > > > That's the route that GNU coreutils has taken recently; in the unlikely > case perl is ab

Re: Help2man and Parallel Make Race

2012-11-19 Thread Stefano Lattarini
On 11/19/2012 08:55 PM, Neil T. Dantam wrote: > > Hi, > > I'm using help2man to build manpages that I'd like to distribute with > the source tarball. I followed the instructions/example in the > automake manual, which has manpage foo.1 depend on foo.c and > configure.ac, then does a recursive ma

Help2man and Parallel Make Race

2012-11-19 Thread Neil T . Dantam
Hi, I'm using help2man to build manpages that I'd like to distribute with the source tarball. I followed the instructions/example in the automake manual, which has manpage foo.1 depend on foo.c and configure.ac, then does a recursive make to build foo$(EXEEXT):

Re: looking for a good example of non-recursive Make using project

2012-11-19 Thread Bob Friesenhahn
On Mon, 19 Nov 2012, Eric Blake wrote: You can reduce the pain by using variables: more = more prog_SOURCES += ${more}/file3.c ${more}/file4.c so that a rename now only has to touch the 'more =' line, rather than every use. The most serious problem is this incantation for 'prog' output to s

Re: Do not distribute files in python_PYTHON primary?

2012-11-19 Thread Nate Bargmann
* On 2012 19 Nov 11:37 -0600, Diego Elio Pettenò wrote: > On 19/11/2012 08:55, Nate Bargmann wrote: > > Is there a way to use the python_PYTHON primary but not distribute the > > file(s) in its list? > > nodist_python_PYTHON should do the trick Thanks, Diego. That works just as I want. I'm not

Re: Do not distribute files in python_PYTHON primary?

2012-11-19 Thread Diego Elio Pettenò
On 19/11/2012 08:55, Nate Bargmann wrote: > Is there a way to use the python_PYTHON primary but not distribute the > file(s) in its list? nodist_python_PYTHON should do the trick -- Diego Elio Pettenò — Flameeyes flamee...@flameeyes.eu — http://blog.flameeyes.eu/

Do not distribute files in python_PYTHON primary?

2012-11-19 Thread Nate Bargmann
The library project I am maintaining has various language bindings generated by the Swig package. Each of the language bindings are enabled by an Automake conditional. As there were various files being generated no matter if a language binding was enabled or not, I've set about trying to correct

Re: looking for a good example of non-recursive Make using project

2012-11-19 Thread Eric Blake
On 11/19/2012 12:51 AM, NightStrike wrote: > If you include src/more/Makefile.am into src/Makefile.am (a perfectly > valid thing to do), you will be unpleasantly surprised that > src/more/Makefile.am has to actually know where it is in the source > tree. It needs lines like this: > > prog_SOURCES

Re: looking for a good example of non-recursive Make using project

2012-11-19 Thread Bob Friesenhahn
On Sun, 18 Nov 2012, NightStrike wrote: If you include src/more/Makefile.am into src/Makefile.am (a perfectly valid thing to do), you will be unpleasantly surprised that src/more/Makefile.am has to actually know where it is in the source tree. It needs lines like this: This is something I comp

Re: Splitting "make check" into separate build and run targets

2012-11-19 Thread Stefano Lattarini
On 11/19/2012 01:03 PM, Björn Stenberg wrote: > Stefano Lattarini wrote: >> You could add a dummy dependency for these missing sources, so that make >> won't try to rebuild them (and fail, because there are no rules to do so): > > Yay, that is a neat workaround which I hadn't seen before. > > How

Re: Splitting "make check" into separate build and run targets

2012-11-19 Thread Björn Stenberg
Stefano Lattarini wrote: > You could add a dummy dependency for these missing sources, so that make > won't try to rebuild them (and fail, because there are no rules to do so): Yay, that is a neat workaround which I hadn't seen before. However, this requires me to create a custom input for each p

Re: Splitting "make check" into separate build and run targets

2012-11-19 Thread Björn Stenberg
NightStrike wrote: > > The "check" target depends on the test programs, which in turn depend on > > their source code files. > > make check-TESTS should suffice to do the actual running of the tests, no? No. The check-TESTS target depends on $(TESTS), which in turn depend on their respective sou

Fwd: looking for a good example of non-recursive Make using project

2012-11-19 Thread Vincent Torri
and reply to the list too... -- Forwarded message -- From: Vincent Torri Date: Sat, Nov 17, 2012 at 1:53 PM Subject: Re: looking for a good example of non-recursive Make using project To: Václav Zeman On Sat, Nov 17, 2012 at 1:35 PM, Václav Zeman wrote: > On 11/17/2012 11:36