Experimental Physics and Industrial Control System
|
Hi Luciano,
On 2011-12-01 Piccoli, Luciano wrote:
>
> This problem would have easily been caught if the configure/Makefile had
> the CHECK_RELEASE=YES. It was set to NO in the module I used as a starting
> point.
CHECK_RELEASE also has a WARN setting which I would always recommend using
instead of NO if you need to override an inconsistency (and you understand
what you're doing). Maybe setting it to NO should print a warning?
- Andrew
--
Optimization is the process of taking something that works and
replacing it with something that almost works, but costs less.
-- Roger Needham
- Replies:
- RE: Asyn: "devAsynInt32::initCommon Link must be INST_IO" Piccoli, Luciano
- References:
- Asyn: "devAsynInt32::initCommon Link must be INST_IO" Piccoli, Luciano
- RE: Asyn: "devAsynInt32::initCommon Link must be INST_IO" Piccoli, Luciano
- RE: Asyn: "devAsynInt32::initCommon Link must be INST_IO" Piccoli, Luciano
- Navigate by Date:
- Prev:
RE: Asyn: "devAsynInt32::initCommon Link must be INST_IO" Piccoli, Luciano
- Next:
RE: Asyn: "devAsynInt32::initCommon Link must be INST_IO" Piccoli, Luciano
- 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: Asyn: "devAsynInt32::initCommon Link must be INST_IO" Piccoli, Luciano
- Next:
RE: Asyn: "devAsynInt32::initCommon Link must be INST_IO" Piccoli, Luciano
- 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
|
ANJ, 18 Nov 2013 |
·
Home
·
News
·
About
·
Base
·
Modules
·
Extensions
·
Distributions
·
Download
·
·
Search
·
EPICS V4
·
IRMIS
·
Talk
·
Bugs
·
Documents
·
Links
·
Licensing
·
|