Re: bug#13524: Improving user experience for non-recursive builds

On 2013-02-03 21:42, Stefano Lattarini wrote: > I've pushed the promised patches to the rewindable branch > 'experimental/preproc' (based off of maint). I'll also soon > send them to the list to simplify review (I will drop the > bug tracker from CC:, to avoid cluttering up the report). > > As us

[PATCH 3/6] preproc: prefer '{D}' over '&{D}&' (and similarly for other substs)

The new form is shorter, easier and more natural to type, and less likely to get wrong due to typos or distractions. Such issues with the '&{FOO}&' form (originally suggested by myself, oops) have been made clear and evident by the recent work on the tests checking the new preprocessing features (

[PATCH 4/6] preproc: better (long) name for built-in '{...}' substitutions

Rename them like this: * {CURDIR} => {RELDIR} * {CANON_CURDIR} => {CANON_RELDIR} The name "CURDIR" was a little ambiguous and potentially confusing, because it could get mixed up with the concept of "current directory" for the executing recipes (which will generally not be the same as the '{C

[PATCH 2/6] preproc: enhance and extend tests

* t/preproc-demo.sh: New test, a "demo" of how the new pre-processing feature could be used in a real-world package. * t/preproc-errmsg.sh: New test, check that error messages remain useful when the new pre-processing features are involved. * t/curdir.sh: Split up ... * t/preproc-basics.sh, t/prepr

[PATCH 6/6] automake: fixups for read_am_file() and calling code

* automake.in (read_am_file): Adjust function prototype (was requiring only two arguments, rather than three). Rename the parameter '$curdir' to the more correct '$reldir'. Rename the local variable '$cur_dir' to the more appropriate and less confusing '$reldir_canon', and avoid continuously re-c

[PATCH 5/6] NEWS: improve wording about new {RELDIR} preproc support

Signed-off-by: Stefano Lattarini --- NEWS | 9 + 1 file changed, 5 insertions(+), 4 deletions(-) diff --git a/NEWS b/NEWS index 938fac8..6aa7060 100644 --- a/NEWS +++ b/NEWS @@ -102,10 +102,11 @@ New in 1.13.2: * Current directory in makefile fragments: - - Use the special makefile

Re: bug#13435: Please don't kill DJGPP support...

Reference: On 01/28/2013 02:55 PM, Stefano Lattarini wrote: > On 01/23/2013 01:16 PM, Stefano Lattarini wrote: >> On 01/14/2013 11:29 PM, DJ Delorie wrote: >>> >>> Stefano Lattarini wrote: Well, then it appear we might actually have no

[PATCH 1/6] preproc: add support for relative names in included fragments

From: Peter Rosin The rationale for this change is that it is annoying to have to repeat the directory name when including a Makefile fragment. For deep directory structures these repeats can generate a lot of bloat. It also hinders reuse and easy directory restructuring if all Makefile fragment

[PATCH 0/6] Add support for relative names in included fragments

Reference: Peter Rosin (1): preproc: add support for relative names in included fragments Stefano Lattarini (5): preproc: enhance and extend tests preproc: prefer '{D}' over '&{D}&' (and similarly for other substs) preproc: better (long

Re: bug#13524: Improving user experience for non-recursive builds

tags 13524 + patch thanks [+cc automake-patches] Reference: On 01/28/2013 12:38 AM, Peter Rosin wrote: > Hi Stefano, > > On 2013-01-27 20:21, Stefano Lattarini wrote: >>> This time with documentation and a NEWS entry. I also fixed the case >>