[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Strategy to specify major, minor, and patch versions
|
From: |
Eric Blake |
|
Subject: |
Re: Strategy to specify major, minor, and patch versions |
|
Date: |
Fri, 29 Aug 2014 08:18:56 -0600 |
|
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.7.0 |
On 08/29/2014 08:01 AM, Shawn H Corey wrote:
> I'm new to all this but can this be done?
>
> m4_define([MAJOR_VERSION], [1])
> m4_define([MINOR_VERSION], [0])
> m4_define([PATCH_VERSION], [0])
> m4_define([VERSION],[MAJOR_VERSION.MINOR_VERSION.PATCH_VERSION])
>
> AC_INIT(foo,[VERSION])
Sure, but again, you probably want to call:
AC_INIT([foo], VERSION)
instead (quote the package name, so that it is used as a name an not an
expansion of a possible macro foo; leave VERSION unquoted so that it
expands as an m4 macro right away before being an argument to AC_INIT).
--
Eric Blake eblake redhat com +1-919-301-3266
Libvirt virtualization library http://libvirt.org
signature.asc
Description: OpenPGP digital signature
- 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 <=
- 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, Peter Johansson, 2014/08/27