From b432fa5f2609e19fa6711d7f857f2a0d7007660d Mon Sep 17 00:00:00 2001 From: Carsten Schoenert Date: Sat, 20 May 2017 11:50:59 +0200 Subject: [PATCH] configure.ac: adding a release-state string To do a more finely graduated versioning a extra new field for the release-state is added. The purpose is mainly to add some extra information about the development state of libcoap like a alpha state right after a final release or marking the state as a release candidate before a planned release. Starting with a string 'alpha' as we are in a really early development state for the upcoming release. --- configure.ac | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-) diff --git a/configure.ac b/configure.ac index 4755819a..4d84a049 100644 --- a/configure.ac +++ b/configure.ac @@ -11,7 +11,12 @@ m4_define([libcoap_major_version], [4]) m4_define([libcoap_minor_version], [2]) m4_define([libcoap_micro_version], [0]) -m4_define([libcoap_version],[libcoap_major_version.libcoap_minor_version.libcoap_micro_version]) +# define a appending release state if needed, for example for pre-releases +# like 'alpha' or 'rc1', for a full release keep the value empty! +m4_define([libcoap_release_state], [alpha]) + +# concatenate the full libcoap version string +m4_define([libcoap_version], [m4_format([%s.%s.%s%s], libcoap_major_version, libcoap_minor_version, libcoap_micro_version, libcoap_release_state)]) AC_INIT([libcoap], [libcoap_version], [libcoap-developers@lists.sourceforge.net], [libcoap], [https://libcoap.net/]) AC_PREREQ([2.64])