[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: non-recursive automake advice?

From: Bob Friesenhahn
Subject: Re: non-recursive automake advice?
Date: Mon, 29 Aug 2005 18:14:08 -0500 (CDT)

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 '' files I need to remember to qualify every
filename with not just '$(srcdir)', but
'$(srcdir)/modules_directory_name/'.  This is only a minor annoyance
and definitely worth the trouble, but perhaps I am missing something?

Anyway my real issue is that I just can't get the build system to find
the module-archives correctly.  If I do (for example):

Any Automake target name which would contain directory separators needs to have the directories separators replaced with underscores in the name. This can be painful. Also keep in mind that regardless of inclusion, Automake is not going to treat content differently based on where it is included from. Therefore, your sub-directory files are going to have to know that they are located in a sub-directory and need to use "full paths" from the directory where the top is located.

Am I going about this completely the wrong way?  Is there some software
I can look at for an example of a 'correct' way to do this?

Development GraphicsMagick 1.2 does use a completely non-recursive build. It uses Automake includes to include per-subdirectory .am files as you mention. A tarball may be downloaded from ""; or you may look at the files via cvsweb at "";.

You will notice that the files don't use += at all. I don't know that there is anything wrong with using += but I felt more secure with using named variables and explicit concatenation for everything since I could be absolutely sure about ordering.

Bob Friesenhahn
GraphicsMagick Maintainer,

reply via email to

[Prev in Thread] Current Thread [Next in Thread]