Re: unwanted added compiler arguments
Arthur Gruzauskas <[email protected]>
| Newsgroups | gmane.comp.kde.users.kdevelop |
|---|---|
| Message-ID | <5635131.v7jOYN4pYs@snowy> |
Thanks Guys. Using "set(CMAKE_CXX_STANDARD 14)" solved some issue I had awhile back, forgotten what. BTW setting it to 17 produces a whole swag of errors I would rather leave for a super brain day. Removing set(CMAKE_CXX_STANDARD 14) set(CMAKE_CXX_STANDARD_REQUIRED ON) set(CMAKE_CXX_EXTENSIONS OFF) now it appends "-fPIC -std=gnu++11" to my build panel command line... So not a KDevelop issue, I'll stop bothering you. And I now have somewhere else to fiddle with this puzzle. CMake exploring, here I come! Arthur, who appreciates your quick and useful help On Monday, 30 October 2017 2:06:46 PM AEDT René J.V. Bertin wrote: > On Monday October 30 2017 13:48:24 Aleix Pol wrote: > >It seems logical to me that c++14 is passed if you specify > >"set(CMAKE_CXX_STANDARD 14)". > > My thoughts exactly. > > CMake has a habit of appending its arguments after any you set yourself, > unless you target the appropriate variables for the build type you've > chosen. Or unless you select a custom build type, like Debian and Ubuntu do > (or used to do? CMAKE_BUILD_TYPE=Debian). But I guess that even in that > case arguments to come from settings like the one above will get appended > (and that would actually make sense). > > R.