Hi!
Ralf Wildenhues writes:
> Hmm, or do both:
> foo_SOURCES += %ADDPREFIX%(%AM_PREFIX%,
> file1.c file2.c ...)
>
> in sub/fragment.am, and with
> include $(srcdir)/sub/fragment.am
>
> would expand (at automake run time) to
> foo_SOURCES += sub/file1.c sub/file
On Mon, 2 Aug 2010, Bernd Jendrissek wrote:
What about taking a cue from nobase_FOOS and having
prefixed_nobase1_dist_SOURCES =
perl/Foo/Bar.pm \
perl/Foo/Baz.pm
I'm deliberately conflating another issue: the all-or-nothing nature
of nobase_FOOS. In some source trees, it forces you to have
On Mon, Aug 2, 2010 at 1:15 AM, Bob Friesenhahn
wrote:
> My experience has been that the target names are the biggest chore with a
> non-recursive build since it is common to place targets in the same
> directory level as the source code. Providing a short-hand which allows
> elimination of foo_b
On Sun, 1 Aug 2010, Ralf Wildenhues wrote:
Ludovic (and others?) suggested a different approach for easier file
name handling in nonrecursive makefile setups: provide GNU make-like
substitution functions, such as addprefix. They could be expanded at
automake run time to still produce portable m
Ludovic (and others?) suggested a different approach for easier file
name handling in nonrecursive makefile setups: provide GNU make-like
substitution functions, such as addprefix. They could be expanded at
automake run time to still produce portable makefiles.
I'm torn between this and my earlie
