Re: defining make vars

[Reinhold Kainhofer]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Am Dienstag, 8. September 2009 01:19:11 schrieb Graham Percival:
> I'm looking at automatically replacing download links in
> general.texi (and subfiles) with macros.  I think that's the best
> way to deal with them; we already have the @version macro that's
> auto-generated.
>
> @version is defined from TOPLEVEL_VERSION, which in turn is
> defined from TOPLEVEL_MAJOR_VERSION (etc).  But how is
> TOPLEVEL_MAJOR_VERSION defined?  I'm guessing that one of the
> makefiles or stepmake stuff actually reads from /VERSION, but I
> can't figure out which piece of the build system does it.

TOPLEVEL_VERSION is an (auto)make variable, defined in aclocal.m4:

    . $srcdir/VERSION
    FULL_VERSION=$MAJOR_VERSION.$MINOR_VERSION.$PATCH_LEVEL
    MICRO_VERSION=$PATCH_LEVEL
    TOPLEVEL_VERSION=$FULL_VERSION

The first line above reads in the VERSION file, the second constructs the 
FULL_VERSION from the various parts defined in the VERSION file...

Notice that aclocal.m4 also calls AC_SUBST on each $*_VERSION part, so these 
variables are available in makefiles...

Cheers,
Reinhold
- -- 
- ------------------------------------------------------------------
Reinhold Kainhofer, address@hidden, http://reinhold.kainhofer.com/
 * Financial & Actuarial Math., Vienna Univ. of Technology, Austria
 * http://www.fam.tuwien.ac.at/, DVR: 0005886
 * LilyPond, Music typesetting, http://www.lilypond.org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)

iD8DBQFKpahiTqjEwhXvPN0RAi6oAJ4m6VrqVr94TilcDpWlQBf7YFL35gCeL5Cp
MWP9rhlkApM8/uYWSRaDr1g=
=xZt1
-----END PGP SIGNATURE-----