Hello, You might want to check these out (if you don’t already know it) (And possibly vote) if you read the comments in (I think it was the type renderers or qt-project file support one) there was some useful info
https://youtrack.jetbrains.com/issue/CPP-274 <https://youtrack.jetbrains.com/issue/CPP-274> https://youtrack.jetbrains.com/issue/CPP-318 <https://youtrack.jetbrains.com/issue/CPP-318> https://youtrack.jetbrains.com/issue/CPP-605 <https://youtrack.jetbrains.com/issue/CPP-605> Best, Emre > On 1 Oct 2018, at 17:58, Steve Atkins <st...@blighty.com> wrote: > > (I'm asking here because I think my odds of finding a CLion user in a pile of > Qt users is better than finding a Qt user in a bucket of CLion users). > > I have a medium-sized Qt+cmake project - it builds fine, Qt Creator is > mostly[1] happy with it. I thought I'd give CLion a try, and it really > doesn't seem to like Qt. > > A simple header file that has "#include <QString>" at the top has most of the > QString member variables underlined in red with hover text of "Field has > incomplete type 'QString'". > > Any use of qCWarning says "No matching function for call to qWarning". > QStringLiteral says "Expected body of lambda expression". > > Despite all the errors in the editor it builds fine from within CLion. > > Has anyone used CLion with Qt successfully? If so, any suggestions for how to > make it happy? > > > Cheers, > Steve > > [1] It has the clangbackend crashing issue, but that's about it. > _______________________________________________ > Interest mailing list > Interest@qt-project.org > http://lists.qt-project.org/mailman/listinfo/interest
_______________________________________________ Interest mailing list Interest@qt-project.org http://lists.qt-project.org/mailman/listinfo/interest
