diff options
| author | Tom Tromey <tromey@redhat.com> | 2001-07-17 05:53:49 +0000 |
|---|---|---|
| committer | Tom Tromey <tromey@redhat.com> | 2001-07-17 05:53:49 +0000 |
| commit | 1c4a810c9532083e2193bf16e54dc34ae8d042f0 (patch) | |
| tree | 4b5750899586819a2370453dcaa1bdd06d72cc51 /HACKING | |
| parent | 8c00243eb6bb22080843307e5fb02316009251c0 (diff) | |
| download | automake-1c4a810c9532083e2193bf16e54dc34ae8d042f0.tar.gz | |
Report from Motoyuki Kasahara:
* tests/make.test: Use am__include.
* tests/exsource.test: Use am__include.
* m4/make.m4 (AM_MAKE_INCLUDE): Use am__include and am__quote.
* automake.in (handle_languages): Use am__include and am__quote.
Diffstat (limited to 'HACKING')
| -rw-r--r-- | HACKING | 8 |
1 files changed, 6 insertions, 2 deletions
@@ -37,11 +37,15 @@ = Naming * We've adopted the convention that internal AC_SUBSTs should be - named with a leading `_am_', and internally generated targets should - be named with a leading `_am-'. This convention is very new + named with a leading `am__', and internally generated targets should + be named with a leading `am--'. This convention is very new (as of Feb 7 2001) and so it isn't yet universally used. But all new code should use it. + We used to use `_am_' as the prefix for an internal AC_SUBST. + However, it turns out that NEWS-OS 4.2R complains if a Makefile + variable begins with `_'. Yay for them. I changed the target + naming convention just to be safe. ================================================================ = Editing `.am' files |