Hello everybody,
Since i upgraded to Qt 5.5, i get a lot (something like 30.000) warnigns
from clang. I have this version installed:
Apple LLVM version 6.1.0 (clang-602.0.53) (based on LLVM 3.6.0svn)
Target: x86_64-apple-darwin14.4.0
Thread model: posix
It's alway the same warning:
Hello,
Yes, I can update the documentation when the changes have been approved and
merged.
Cheers,
Leena
Leena Miettinen | Documentation Engineer | The Qt Company
Digia Germany GmbH, Rudower Chaussee 13, D-12489 Berlin
Geschäftsführer: Mika Pälsi, Juha Varelius, Tuula Haataja
Sitz der
No trying to be difficult here so here goes. I created a qtlogging.ini in
~/Library/Preferences and inside several locations in the QtCreator.app
package. Reading through the web page does not tell me where to look for the
log file. I looked in all the usual locations on OS X include /var/log
Also are there certain arguments that QtCreator uses with libClang? Things
like -Wall or something that has an equivalent clang command line argument?
Maybe if I put those into my compile specification I can have my compiler
produce the same warnings?
Also, how can I force QtCreator to reindex
Hi Kikolai,
Looks like a bug on Windows - there I also get the +2 lines difference.
I agree with you, on Linux I was able to implement your suggestion and now
my SpellChecker works correctly for QStringLiterals. PS: I have no way to
test on Mac so the code will be enabled if building from
Hi,
this output will be printed on stdout/stderr by default. So, you have to start
QC from cmdline using sth similar to
PATH_TO_QC_APP_BUNDLE/Qt\ Creator.app/Contents/MacOS/Qt\ Creator
to see this output. Don't know exactly where this output goes if you're just
open the app bundle itself or
Hi!
Enable the following logging categories [1] to get output from libclang:
qtc.clangcodemodel.clangeditordocumentparser=true
qtc.clangcodemodel.verboserun=true
Here is how you can help:
* Do not use the mailing list for bug reports.
* Create a report at https://bugreports.qt.io/
