Subject: |
Re: Version strings to track not only EPICS BASE but other IOC modules/components |
From: |
Michael Davidsaver <[email protected]> |
To: |
[email protected] |
Date: |
Tue, 24 Sep 2013 12:04:16 -0400 |
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
- References:
- Version strings to track not only EPICS BASE but other IOC modules/components Williams Jr., Ernest L.
- Navigate by Date:
- Prev:
Re: Version strings to track not only EPICS BASE but other IOC modules/components Rod Nussbaumer
- Next:
Channel Access in Erlang paper at ICALEPCS 2013 Dennis Nicklaus
- Index:
1994
1995
1996
1997
1998
1999
2000
2001
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
2012
<2013>
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
- Navigate by Thread:
- Prev:
Re: Version strings to track not only EPICS BASE but other IOC modules/components Rod Nussbaumer
- Next:
Channel Access in Erlang paper at ICALEPCS 2013 Dennis Nicklaus
- Index:
1994
1995
1996
1997
1998
1999
2000
2001
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
2012
<2013>
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
|