Re: Version strings to track not only EPICS BASE but other IOC modules/components

[Michael Davidsaver <mdavidsaver@bnl.gov>]

For some of my projects I compile in a VCS revision number (for us 
Mercurial and/or Git) which appears in a stringin record.  This has 
proven useful in keeping track of my ~40 timing VME crates.

A (poor) example can be found in the mrfioc2 module.  I say poor because 
it is regenerating a C header file regardless of whether this is needed, 
which triggers a recompile and relink every time make is invoked.

I too would like to see a standard solution.

Michael


http://epics.hg.sourceforge.net/hgweb/epics/mrfioc2/file/9f6e261d3ea9/mrfCommon/src/Makefile#l94

http://epics.hg.sourceforge.net/hgweb/epics/mrfioc2/file/9f6e261d3ea9/mrfCommon/src/mrf/version.h


On 09/24/2013 10:25 AM, Williams Jr., Ernest L. wrote:
> Hi everyone,
>
> How might one use the same scheme to supply a version string to reflect the version of a software module?
>
> Does EPICS Toolkit support this for Driver/Device Support?
>
> Would also be nice to have a version string supported for IOC applications as well.
>
> Can this be done in a standardized way such as dbior()?
>
> For example, EPICS BASE uses:
> "$EPICS_BASE_RELEASE/configure/CONFIG_SITE"
> Variable NAME = EPICS_SITE_VERSION
>
> Then at the ioc shell  coreRelease() will print out the version string.
>
> So, for an EPICS module maybe:
> <moduleName>Release()
>
> For an IOC Application:
> <iocAppName>Release()
>
> This would be very useful and can also be place in a PV :)
>
> Anyone already doing this?  If so, can we get it standardized as part of the EPICS BASE and templates?
>
>
> Cheers,
> Ernest