f35 kdevelop 5.6.2 :: within project sting_view not found in std?

[Adrian Sevcenco]

Hi!

On 11.02.2022 15:10, René J.V. Bertin wrote:
> On Friday February 11 2022 14:15:14 Adrian Sevcenco wrote:
> 
>> and that std=c++11 is just wrong... any idea how can i instruct the clang parser to used c++17?
> 
> The prefs tab where you select the dialect to use also has a text entry for setting custom arguments passed to the
you mean in the project?
actually, with am empty project just for my application i made sure to have this:
https://prntscr.com/26tsaq6

> parser. Normally that is inactive (text greyed out) and should use the value from the dialect selector, but it
> probably doesn't if it somehow got modified manually into a custom set of arguments. And it's not impossible that
> this happens when you just click in the entry field. Either way, you can set the appropriate std argument there.
also i checked the project file to have the relevant info:
grep parserArguments ao2dproto.kdev4
parserArguments=-ferror-limit=100 -fspell-checking -Wdocumentation -Wunused-parameter -Wunreachable-code -Wall -std=c++17
parserArgumentsC=-ferror-limit=100 -fspell-checking -Wdocumentation -Wunused-parameter -Wunreachable-code -Wall -std=c++17
parserArgumentsCuda=-ferror-limit=100 -fspell-checking -Wdocumentation -Wunused-parameter -Wunreachable-code -Wall 
-std=c++14
parserArgumentsOpenCL=-ferror-limit=100 -fspell-checking -Wdocumentation -Wunused-parameter -Wunreachable-code -Wall 
-cl-std=CL2.0

and i stil have in the kdevelop oputput:
Invocation: clang -ferror-limit=100 -fspell-checking  -Wunused-parameter -Wunreachable-code -Wall -std=c++11 -nostdinc 
-nostdinc++ -xc++ -isystem/home/physics-tools/ROOT/v6-26-00-patches/include -isystem/usr/include/c++/11 
-isystem/usr/include/c++/11/x86_64-redhat-linux -isystem/usr/include/c++/11/backward -isystem/usr/local/include 
-isystem/usr/include -isystem /usr/lib64/llvm12/lib/clang/12.0.1/include -imacros /home/adrian/tmp/kdevelop.GsTyiP 
/home.hdd/adrian/work/AO2Dproto/ao2d_process.C

Any other idea where can i fix this?
I apologize if i'm too insistent but after very close to 20 years of kdevelop usage i'm not to keen
to change IDE just because i moved to c++17 ..

Thanks a lot for info and help!!
Adrian


> 
> I suppose that removing the project from your session only limited the amount of output spilled on your terminal,
> right? KDevelop doesn't use cross-project parsing information. Suggestion: turn off the automatic full-project
> parsing on load/startup (in the global settings). That way only the files you open get parsed (+ their headers) which
> saves time and RAM (potentially a lot of both). Plus parsing output on the terminal, if you activate that.
> 
> R.