Back Midas Rome Roody Rootana
  Midas DAQ System  Not logged in ELOG logo
Entry  22 Sep 2025, Konstantin Olchanski, Info, switch midas to c++17 
    Reply  23 Sep 2025, Pavel Murat, Info, switch midas to c++17 
       Reply  23 Sep 2025, Konstantin Olchanski, Info, switch midas to c++17 
          Reply  23 Sep 2025, Pavel Murat, Info, switch midas to c++17 
    Reply  06 Nov 2025, Konstantin Olchanski, Info, switch midas to c++17 
       Reply  20 Nov 2025, Konstantin Olchanski, Info, switch midas to c++17 
          Reply  20 Nov 2025, Nick Hastings, Info, switch midas to c++17 
             Reply  25 Nov 2025, Konstantin Olchanski, Info, switch midas to c++17 
          Reply  24 Nov 2025, Stefan Ritt, Info, switch midas to c++17 
             Reply  25 Nov 2025, Konstantin Olchanski, Info, switch midas to c++17 
Message ID: 3140     Entry time: 25 Nov 2025     In reply to: 3128
Author: Konstantin Olchanski 
Topic: Info 
Subject: switch midas to c++17 
> 
> > I notice the cmake does not actually pass "-std=c++17" to the c++ compiler, and on U-20, it is likely 
> > the default c++14 is used. cmake always does the wrong thing and this will need to be fixed later.
> 
> set(CMAKE_CXX_STANDARD 17)
> set(CMAKE_CXX_STANDARD_REQUIRED ON)
>

We used to have this, it is not there now.

> 
> Get it to do the right thing?
> 

Unlikely, as Stefan reported, asking for C++17 yields -std=gnu++17 which is close enough, but not the same 
thing.

For now, it does not matter, U-22 and U-24 are c++17 by default, if somebody accidentally commits c++20 
code, builds will fail and somebody will catch it and complain, plus the weekly bitbucket build will bomb-
out.

On U-20, default is c++14 and builds will start bombing out as soon as we commit some c++17 code.

el7 builds have not worked for some time now (a bizarre mysterious error)

el8, el9, el10 likely same situation as Ubuntu.

macos, not sure.

K.O.
ELOG V3.1.4-2e1708b5