Weird behavior, if we enable c++11 with "CONFIG += c++11" in src.pro. Everything will compile correctly, but compiler output will say g++ uses -std=c++0x.
If we enable c++11 in assisi-are-ui.pro, compiler will lose -std parameter and will throw many errors for using c++11 features.
In QtCreator docs it is said that gcc/g++ 4.7 or newer should be used. Only way for second method to work (and compiler to use -std=c++11 flag, even in first method) is changing system files which set g++&qt5 preferences (where default is -std=c++0x). It appears that older versions of gcc/g++ don't recognize new flag (and use legacy flag which enables some of c++11 features).
stribor14
commented
7 years ago
Weird behavior, if we enable c++11 with "CONFIG += c++11" in src.pro. Everything will compile correctly, but compiler output will say g++ uses -std=c++0x.
If we enable c++11 in assisi-are-ui.pro, compiler will lose -std parameter and will throw many errors for using c++11 features.
In QtCreator docs it is said that gcc/g++ 4.7 or newer should be used. Only way for second method to work (and compiler to use -std=c++11 flag, even in first method) is changing system files which set g++&qt5 preferences (where default is -std=c++0x). It appears that older versions of gcc/g++ don't recognize new flag (and use legacy flag which enables some of c++11 features).
Even in Xenial repos gcc&g++ are v4:5.3.1.