Hi Ralf,
Thanks for your help.
Unfortunately, due to a last-minute edit in my original message that
I failed to review, I misstated something: the (single) built
application executable should reside in AppDir, *not* in any of the
subdirectories (as my original mail incorrectly stated). Sorry for
the mistake.
Anyway, your solution of simply listing subdirectories in SUBDIRS,
without any targets, in the TopDir Makefile did indeed solve my
problem. I was already listing them, but assumed I needed to have
some form of binary target listed in my Makefile.am. I'm not sure if
this particular point (that a valid Makefile.am need not explicitly
list any targets) is as obvious as it might be in the automake
documentation.
Thanks again, -jar
On Sep 9, 2008, at 2:41 PM, Ralf Wildenhues wrote:
Hello John,
* John Richetta wrote on Tue, Sep 09, 2008 at 11:32:01PM CEST:
I have a project that has a directory structure like this:
TopDir
|
+----------------+----+
| | |
AppDir other dirs...
| |
A B
The top level of this project is where one invokes configure and
make.
However, the project has traditionally been structured such that the
final executable resides in subdirectories of AppDir, and the actual
source code primarily resides in subdirs of AppDir.
Example:
TopDir/Makefile.am:
SUBDIRS = AppDir ...
AppDir/Makefile.am:
bin_PROGRAMS = A/proggie_one
A_proggie_one_SOURCES = B/source1.c A/sub/source2.c ...
AUTOMAKE_OPTIONS = subdir-objects
There is no reason to build a dummy program with no sources.
Hope that helps.
Cheers,
Ralf
