Qt Creator Clang Code Model: Difference between revisions
Jump to navigation
Jump to search
| Line 11: | Line 11: | ||
$ set QT_LOGGING_RULES=qtc.clang*=true | $ set QT_LOGGING_RULES=qtc.clang*=true | ||
$ qtcreator.exe | $ qtcreator.exe | ||
The debugging output contains among others: | |||
* The IPC messages send/received | |||
* Output of libclang while parsing | |||
=== Internal command line === | === Internal command line === | ||
| Line 16: | Line 20: | ||
However, to see also the resulting internal command line of libclang run: | However, to see also the resulting internal command line of libclang run: | ||
# | # Switch to projects mode and there to the "Clang Code Model" | ||
# Copy some warning configuration by clicking on "Copy...", give it a name like "Debug" | # Copy some warning configuration by clicking on "Copy...", give it a name like "Debug" | ||
# Replace all the options from the copied configuration with "-###" | # Replace all the options from the copied configuration with "-###" | ||
Revision as of 10:32, 8 April 2016
Documentation: http://doc.qt.io/qtcreator/creator-clang-codemodel.html
Debugging
QLoggingCategory is used for debugging output. With the following invocation debugging output will be generated:
Linux/Mac: $ QT_LOGGING_RULES=qtc.clang*=true ./qtcreator
Windows (start DebugView in advance to see the output): $ set QT_LOGGING_RULES=qtc.clang*=true $ qtcreator.exe
The debugging output contains among others:
- The IPC messages send/received
- Output of libclang while parsing
Internal command line
The debugging output from above will contain all the command line options that are passed on to libclang, which is enough for most cases.
However, to see also the resulting internal command line of libclang run:
- Switch to projects mode and there to the "Clang Code Model"
- Copy some warning configuration by clicking on "Copy...", give it a name like "Debug"
- Replace all the options from the copied configuration with "-###"
- Close and re-open the editor document - the new debugging output will contain also the internal command line
Note that libclang/clangbackend will crash afterwards, so do not forget to switch back to a sane warning configuration.