[Top][All Lists]

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

Re: Public header files

From: Peter Johansson
Subject: Re: Public header files
Date: Sun, 21 Mar 2010 15:16:05 -0400
User-agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.4; en-US; rv: Gecko/20100227 Thunderbird/3.0.3

Hi Jef,

On 3/17/10 8:23 AM, Jef Driesen wrote:
I only need it compiled into my library. The goal is that an application using my library can report the exact revision of the library (for diagnostic purpose).

With the solution I outlined in my previous posts, I can already get the "normal" version info (e.g. the major.minor.micro numbers) into a public header file to allow for compile time version checking. Runtime version checking can easily be achieved by adding a mylib_get_version() function to the library. But when building not yet released code, it's more useful to know the exact SCM revision, rather than the version numbers.

I compile the svn revision into my program so it can be included in `--version output'. It is based on a solution described here

I've modified it a bit to avoid unnecessary compilations and to allow building from an 'svn export'. You can see the details on how it is done here

In short, we use two different modes. 1) If we are building from svn wc and 2) if we are building from a tarball or svn export. We test which mode we're in by detecting `$srcdir/.svn' at configure time and create a automake conditional. In case 1) we use svnversion (included in subversion) to create from, whereas in case 2) we do not touch

I hope that helps and if you have any question please let me know.


reply via email to

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