[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Strategy to specify major, minor, and patch versions

Subject: Re: Strategy to specify major, minor, and patch versions
Date: Fri, 29 Aug 2014 19:55:53 +0100
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Icedove/24.6.0

On 08/29/2014 03:01 PM, 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])


That's odd. When I add the m4_define([VERSION],...) command to my script and run make, the build process throws a bunch of warning and error messages. The build process manages to stop due to an error, whose error message is as follows:

configure: error: C compiler cannot create executables

After checking the output in config.log, I find this:

address@hidden:build$ tail config.log
#define PACKAGE_NAME "foo"
#define PACKAGE_TARNAME "foo"
#define PACKAGE_VERSION "1.0.0"
#define PACKAGE_STRING "foo 1.0.0"
#define PACKAGE_URL ""
#define PACKAGE "foo"
#define 0.0.0 "x.0.0"

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.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]