Back Midas Rome Roody Rootana
  Midas DAQ System  Not logged in ELOG logo
Entry  12 Dec 2024, Stefan Ritt, Suggestion, New alarm sound flag to be tested 
    Reply  19 Dec 2024, Stefan Ritt, Suggestion, New alarm count added 
       Reply  20 Mar 2025, Konstantin Olchanski, Suggestion, BINARY INCOMPATIBLE CHANGE: New alarm count added 
          Reply  21 Mar 2025, Stefan Ritt, Suggestion, BINARY INCOMPATIBLE CHANGE: New alarm count added 
             Reply  21 Mar 2025, Konstantin Olchanski, Suggestion, BINARY INCOMPATIBLE CHANGE: New alarm count added 
Message ID: 2964     Entry time: 20 Mar 2025     In reply to: 2925     Reply to this: 2980
Author: Konstantin Olchanski 
Topic: Suggestion 
Subject: BINARY INCOMPATIBLE CHANGE: New alarm count added 
> ALL MIDAS CLIENTS GET RE-COMPILED after the new code is applied.

Usually we expect that it is "safe" to update to the latest version of MIDAS.

In the sense that we do not have to track down every single frontend
and rebuild it. We have several experiments where tracking down the source code
and rebuilding a frontend takes more than 5 seconds. In many cases these are
10 year old executables that worked just fine through many updates of MIDAS
without having to rebuild them.

So any binary incompatible change is best avoided and must be clearly announced.

The present binary-incompatible change is this commit:
https://bitbucket.org/tmidas/midas/commits/5899f1657ba31121c9f420a824b3c6c13b173988

I tagged the last commit before this change as: midas-2024-12-a

K.O.
ELOG V3.1.4-2e1708b5