[Qt-creator] clangd + qtc vs clangd + any editor

Cristian Adam cristian.adam at qt.io
Wed Mar 1 21:41:25 CET 2023


As a C++ developer you could actually fix something in Qt Creator. If it's something minor you can simply fork qt-creator on github, push to your fork and you'll get binaries created by GitHub Actions.

There are not so many C++ IDEs written in C++, open source, and cross-platform!

This was important for me before joining the Qt Creator team and working on Qt Creator itself.


From: Qt-creator <qt-creator-bounces at qt-project.org> on behalf of Knut Petter Svendsen via Qt-creator <qt-creator at qt-project.org>
Sent: Thursday, February 23, 2023 06:38
To: qt-creator at qt-project.org <qt-creator at qt-project.org>
Subject: [Qt-creator] clangd + qtc vs clangd + any editor

I often get asked by my coworkers why I use qtcreator for general C++
development (non-Qt) when you can use clangd with "any" editor and get
code completion, navigation, refactoring etc. Often they mention vscode
and/or vim.

Assuming that you have a build system in place that can generate a
compile_commands.json file, which advantages does QtCreator give? (non-Qt

I do have a personal preference for QtCreator, but I would greatly
appreciate it if you could provide me with some insight on the matter.

Knut Petter Svendsen

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/qt-creator/attachments/20230301/89753c78/attachment.htm>

More information about the Qt-creator mailing list