Experimental Physics and
Industrial Control System

"Shankar, Murali" <[email protected]> · Wed, 20 Feb 2013 13:00:12 -0800

Got it. Thanks all for your help.

Regards,
Murali

-----Original Message-----
From: Andrew Johnson [mailto:[email protected]] 
Sent: Wednesday, February 20, 2013 11:58 AM
To: [email protected]
Cc: Shankar, Murali
Subject: Re: Best practices for introducing new dot releases of modules.

Hi Murali,

On 2013-02-20 Shankar, Murali wrote:
> So, to test a dot release of the sequencer, should I rebuild all the 
> other modules that the app depends on that also depend on the sequencer?

Yup, that's what you have to do to solve this properly.  Although the new version could be fully compatible with the old one, there is no way for the build system to test that compatibility, so by default it enforces the safest option, which is to not allow the build to continue.  I added the module checking mechanism because in the past linking incompatible modules together has caused numerous some really strange and often extremely subtle bugs to turn up here at APS, in some cases only being noticed days or even weeks after we booted the IOC.

If you as the author of the IOC are certain that the changes did not involve modifying any struct or class definitions, or changing any routines in an incompatible way you can edit your application's configure/CONFIG_SITE file and set CHECK_RELEASE to WARN (it also accepts NO but I don't recommend using
that) which will then allow the build to complete despite the warnings.

- Andrew
--
There is no such thing as a free lunch.  When invited for lunch, it is best to check if you are there to eat, or to be eaten.
-- Clive Robinson

Experimental Physics and Industrial Control System

Experimental Physics and
Industrial Control System