[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Strategy to specify major, minor, and patch versions
|
From: |
Shawn H Corey |
|
Subject: |
Re: Strategy to specify major, minor, and patch versions |
|
Date: |
Fri, 29 Aug 2014 15:58:13 -0400 |
On Fri, 29 Aug 2014 19:55:53 +0100
Zé <address@hidden> wrote:
> So, it appears that defining the VERSION variable ends up replacing
> the VERSION string in the output with the definition provided by the
> newly added m4_define() line.
I thought there might be a conflict. Try:
m4_define([APP_MAJOR_VERSION], [1])
m4_define([APP_MINOR_VERSION], [0])
m4_define([APP_PATCH_VERSION], [0])
m4_define([APP_VERSION],[APP_MAJOR_VERSION.APP_MINOR_VERSION.APP_PATCH_VERSION])
AC_INIT(foo,[APP_VERSION])
AM_INIT_AUTOMAKE(foo,[APP_VERSION])
--
Don't stop where the ink does.
Shawn
- Strategy to specify major, minor, and patch versions, Zé, 2014/08/27
- Re: Strategy to specify major, minor, and patch versions, Eric Blake, 2014/08/27
- Re: Strategy to specify major, minor, and patch versions, Zé, 2014/08/28
- Re: Strategy to specify major, minor, and patch versions, Eric Blake, 2014/08/28
- Re: Strategy to specify major, minor, and patch versions, Zé, 2014/08/29
- Re: Strategy to specify major, minor, and patch versions, Eric Blake, 2014/08/29
- Re: Strategy to specify major, minor, and patch versions, Zé, 2014/08/29
- Re: Strategy to specify major, minor, and patch versions, Shawn H Corey, 2014/08/29
- Re: Strategy to specify major, minor, and patch versions, Eric Blake, 2014/08/29
- Re: Strategy to specify major, minor, and patch versions, Zé, 2014/08/29
- Re: Strategy to specify major, minor, and patch versions,
Shawn H Corey <=
Re: Strategy to specify major, minor, and patch versions, Peter Johansson, 2014/08/27