On Sat, 9 Mar 2013, Harlan Stenn wrote:
I'm not suggesting a single flat file for a non-recursive Makefile
situation.
I'm expecting there to be one Makefile in each directory.
I'd also almost expect that the Makfile in each (build) directory would
"call up" to the top-level Makefile with enoug
Sam Varshavchik writes:
> Harlan Stenn writes:
> > The problem I've had is that the info above does a great job of saying
> > "recursive Make can be a problem" but I haven't found anything to help
> > me make a useful non-recursive Make system.
>
> Non-recursive make systems can be a problem too.
Harlan Stenn writes:
Stefano Lattarini writes:
> My suggestion: if files in different subdirectories are actually
> dependent on each other (that is, the subdirectories are not
> really independent "modules" that can be built independently and
> oblivious to each other), re-organize your build s
Stefano Lattarini writes:
> My suggestion: if files in different subdirectories are actually
> dependent on each other (that is, the subdirectories are not
> really independent "modules" that can be built independently and
> oblivious to each other), re-organize your build system to stop
> using ma
On 03/09/2013 04:09 PM, Sam Varshavchik wrote:
> Consider automake being used together with GNU make and autoconf.
>
> Top level directory 'main'. Two subdirectories, 'a' and 'b'.
>
> main/configure.ac
>
> AC_CONFIGFILES([
>
> ...
>
> a/somefile.inc
>
> ...
>
> ])
>
> main/Makefile.am:
>
>
Consider automake being used together with GNU make and autoconf.
Top level directory 'main'. Two subdirectories, 'a' and 'b'.
main/configure.ac
AC_CONFIGFILES([
...
a/somefile.inc
...
])
main/Makefile.am:
SUBDIRS=a b
main/a/Makefile.am:
data_DATA=somefile.inc
DISTCLEAN=somefile.inc
ma
