标签云

微信群

扫码加入我们

WeChat QR Code

I did follow the suggestions on the documentation to enable clang code completion, but it seems that on the most recent version there is no option to add search paths and compiler flags separately, I tried adding compiler flags on the search path window, but is not showing any evidence that it caught the new paths:Any idea what I'm doing wrong?


it seems to be working now, but only producing completion hints for includes in the '$(shell pkg-config --cflags boost-1.52)' line. The source inside the project itself is being completely ignored

2019年04月19日32分36秒

When you compile your project, do you see codelite-cc in the compiler line? that's the key question here

2019年04月19日32分36秒

yes, the build lines all start with 'codelite-cc clang++ ....'

2019年04月18日32分36秒

When you fail to get input from clang, do you get anything in the 'Clang' tab? (usually there will be an error message there)

2019年04月19日32分36秒

it says 'clang: parsing file <file.cpp>...done'. In some translation units the clang seems to work correctly, and in some others it simply doesn't, the <file.cpp> displays the correct source file, but it doesn't show any error messages. I have both "enable clang" and "inline errors" checkboxes enabled on the clang tab

2019年04月19日32分36秒