Experimental Physics and Industrial Control System
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
- Replies:
- Re: Version strings to track not only EPICS BASE but other IOC modules/components Rod Nussbaumer
- Re: Version strings to track not only EPICS BASE but other IOC modules/components Michael Davidsaver
- Navigate by Date:
- Prev:
Re: EPICS base Installation Error- Need Help Miroslav Mihaylov
- Next:
Re: EPICS base Installation Error- Need Help Vikas Kumthekar
- 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: EPICS base Installation Error- Need Help Pearson, Matthew R.
- Next:
Re: Version strings to track not only EPICS BASE but other IOC modules/components Rod Nussbaumer
- 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