ECM and QNX

Alex Merry alex.merry at kde.org
Sat Oct 18 18:43:18 UTC 2014


On Saturday 18 October 2014 15:32:16 Nicolás Alvarez wrote:
> 2014-10-18 15:28 GMT-03:00 Alex Merry <alex.merry at kde.org>:
> > On Thursday 09 October 2014 13:59:56 Rafael Roquetto wrote:
> >> Hello,
> >> 
> >> KDECompilerSettings.cmake:176 adds -std=c++0x to CMAKE_CXX_FLAGS for GNU
> >> compilers. Would it be possible to pass -std=gnu++0x instead?
> >> 
> >> Rationale:
> >>   The underlying GCC is v4.4, which doesn't know -std=c++11
> >>   yet, only c++0x.
> >>   
> >>   We can't use -std=c++0x here, because the QNX headers
> >>   depend on some GNU extensions (nanosleep() was one that I
> >>   saw), so it has to be gnu++0x, ie. STD C++ + GNU extensions.
> >> 
> >> I am not sure what's the best way to detect a QNX compiler, I am no CMake
> >> expert.
> > 
> > Well, the KDE Frameworks, and hence the applications built on them -- the
> > main users of KDECompilerSettings.cmake -- don't officially support gcc
> > prior to 4.5. So you may well find that you run into problems due to
> > missing features in the compiler.
> 
> 4.5 doesn't support -std=c++11 either.

Ah, I should have actually checked the file. We use the -std=c++0x flag 
anyway, so that's fine, and should work on any supported version. If the QNX 
system headers require a different flag, then, as I said, we can put in a 
workaround, but someone on the QNX system will have to devise and test the 
check for it.

Alex


More information about the Kde-buildsystem mailing list