Re: Non-recursive automake

2009-10-17 Thread Ralf Wildenhues
Hello, * Jan Engelhardt wrote on Sat, Oct 17, 2009 at 07:04:39PM CEST: > when one decides to drive make in a non-recursive fashion, one has to > write an Automake file like this: > > lib_LTLIBRARIES = foo/bar.la > foo_bar_la_SOURCES = foo/one.c foo/two.c > > Usually I stuff that into a file cal

Re: Non-recursive automake

2009-10-17 Thread Robert Collins
On Sat, 2009-10-17 at 20:09 -0500, Bob Friesenhahn wrote: > > I complained about this perhaps five years ago since it is the most > annoying issue related to non-recursive build. There was some > discussion on this list at that time but nothing was done to make > things better. > > It seems t

Re: Non-recursive automake

2009-10-17 Thread Bob Friesenhahn
On Sat, 17 Oct 2009, Jan Engelhardt wrote: when one decides to drive make in a non-recursive fashion, one has to write an Automake file like this: lib_LTLIBRARIES = foo/bar.la foo_bar_la_SOURCES = foo/one.c foo/two.c Usually I stuff that into a file called "foo/Automakefile" and "include foo/A

Non-recursive automake

2009-10-17 Thread Jan Engelhardt
Hi, when one decides to drive make in a non-recursive fashion, one has to write an Automake file like this: lib_LTLIBRARIES = foo/bar.la foo_bar_la_SOURCES = foo/one.c foo/two.c Usually I stuff that into a file called "foo/Automakefile" and "include foo/Automakefile" from the real Makefile.am