Re: non-recursive automake with make 3.81,automake-1.10

2013-07-26 Thread Nick Bowler
Hi, On 2013-07-26 16:53 +0100, Rudra Banerjee wrote: > Hello friends, > In my laptop, I can very well use autotools with the following > Makefile.am : > bin_PROGRAMS = scasr > scasr_SOURCES = src/main.f90\ > src/constants.f90 src/environment.f90 src/util.f90 \ >

Re: Non-recursive automake and double-colon rules

2013-03-25 Thread Nick Bowler
On 2013-03-24 11:33 +, Roger Leigh wrote: > If you switch to non-recursive make (i.e. no use of SUBDIRS), > but you want to use "include" to retain Makefile.ams in > subdirectories, you end up running into problems when you > have multiple copies of -local and -hook rules. [...] > I've used GNU

Re: Non-recursive automake vs. gettext

2011-02-10 Thread Ralf Wildenhues
Hi John, * John Darrington wrote on Wed, Feb 09, 2011 at 07:56:20PM CET: > I like to use a non-recursive makefile structure for my projects. > However, if the project also uses gettext, I end up having to > constantly fight against both gettext and auto{conf,make}. > > If AM_GNU_GETTEXT appears i

Re: Non-recursive automake

2010-01-04 Thread NightStrike
On Sun, Oct 18, 2009 at 1:39 AM, Ralf Wildenhues wrote: > 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_SOURCE

Re: Non-recursive automake

2009-10-18 Thread Robert Collins
On Sun, 2009-10-18 at 08:39 +0200, Ralf Wildenhues wrote: > > http://sources.redhat.com/ml/automake/2001-08/msg00112.html > > > > This added a new directive 'subdir_include' which does an include but > > adjusts all the paths in the make/automake rules in the included > > fragment to the relative

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

Re: non-recursive automake advice?

2005-09-02 Thread Tom Tromey
> "Bob" == Bob Friesenhahn <[EMAIL PROTECTED]> writes: Bob> Note that the messages appear to indicate that Automake does recurse Bob> once regardless. Some features require a $(MAKE) invocation in the same directory. Offhand I forget what. As I recall, removing this would be tricky. Tom

Re: non-recursive automake advice?

2005-08-30 Thread Stepan Kasal
Hello Bob, > % time gmake > gmake all-am > gmake[1]: Entering directory > `/scratch/bfriesen/build/GraphicsMagick-16-static' > gmake[1]: Leaving directory `/scratch/bfriesen/build/GraphicsMagick-16-static' > gmake 0.78s user 0.10s system 88% cpu 0.990 total > % > > Note that the messages appea

Re: non-recursive automake advice?

2005-08-29 Thread Bob Friesenhahn
On Mon, 29 Aug 2005, tom fogal wrote: Your arguments are convincing, I will switch my setup away from convenience archives. As you proceed with your non-recursive build, be sure to keep in mind that you are leaving the common path so you can expect to encounter more bugs or things that need

Re: non-recursive automake advice?

2005-08-29 Thread Bob Friesenhahn
On Mon, 29 Aug 2005, Tom Tromey wrote: "tom" == tom fogal <[EMAIL PROTECTED]> writes: tom> Basically I'd like each module to build their own libtool convenience tom> library, and then have /src/Makefile.am link all of those modules' tom> convenience libraries into one that is the union of all

Re: non-recursive automake advice?

2005-08-29 Thread tom fogal
*mutter*, forgot to cc the list again... --- Forwarded Message From: tom fogal <[EMAIL PROTECTED]> To: Bob Friesenhahn <[EMAIL PROTECTED]> Subject: Re: non-recursive automake advice? In-Reply-To: Your message of "Mon, 29 Aug 2005 18:29:09 CDT." <[EMAI

Re: non-recursive automake advice?

2005-08-29 Thread Tom Tromey
> "tom" == tom fogal <[EMAIL PROTECTED]> writes: tom> Basically I'd like each module to build their own libtool convenience tom> library, and then have /src/Makefile.am link all of those modules' tom> convenience libraries into one that is the union of all of them. Do you really want each sep

Re: non-recursive automake advice?

2005-08-29 Thread Bob Friesenhahn
On Mon, 29 Aug 2005, tom fogal wrote: So I've been convinced that the effort involved in changing a build system to not use recursive make is worth it, and I was wondering if A noble objective. Unfortunately in the 'Inc.am' files I need to remember to qualify every filename with not just '$(