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 my project? Is there a file somewhere that I can delete? The July 30 build seems slightly better in the fact that I don't get the red squiggly under lines any more BUT the code completion does not work for those functions. for example, the line of code has all the same "default text" color which is different that the lines above and below it where my custom colors are used for objects and methods and variables. Thanks Mike Jackson On Jul 30, 2015, at 5:46 AM, Nikolai Kosjar <[email protected]> wrote: > 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/ with the generated output from > the logging categories. > * Attach a minimal project that exhibits the bug so I have sth. *concrete* I > can work with. > > The code snippet and context you provided are not enough. > > The Qt Creator 3.5 rc1 snapshots come with libClang is 3.6, [2] tells me that > XCode 5.x comes with LLVM based on 3.3/3.4. Although that might make a > difference, I doubt it's that for this concrete case. > > Nikolai > > [1] http://doc.qt.io/qt-5/qloggingcategory.html#configuring-categories > [2] https://en.wikipedia.org/wiki/Xcode#Toolchain_versions > _______________________________________________ Qt-creator mailing list [email protected] http://lists.qt-project.org/mailman/listinfo/qt-creator
