This issue was fixed in Qt Creator 11.0.1.

@Crazy-Sage said in How to build Qt with clang under windows?: Clang 7.0.0 And you're sure this ancient compiler supports all MSVC commands when you use clang-cl. What do you think you will gain when you compile Qt with clang-cl at all?

Simply disable this check for clazy in the analyzer settings. CLazy does not know if it's Qt5 or Qt6. In Qt5 QList was not optimal, in Qt6 QVector was renamed to QList ... maybe the next clazy version can somehow fiddle out what Qt version it's currently checking.

Thank you. At least QStrings are shown correctly at the moment (Qt 5.15.2/Xcode 12.5). Don't forget to import the codecs together with the usual imports. import codecs Could not see any differences with the HandleCommand fixes.

this Bash solution didn't work for me, on account of a multi-level project structure that i was dealing with. (at least, i think it was multi-level.) What did work for me was something akin to the following: qmake ./my_project.pro -spec linux-clang CONFIG+=release CONFIG+=DISABLE_DEVELOPER_MODULES CONFIG+=force_debug_info && /usr/bin/make qmake_all make -j $CORES VERBOSE=y all &>make_output.txt compiledb --parse make_output.txt mkdir build/yamls run-clang-tidy -p . -j $CORES -clang-tidy-binary $CLANG_TIDY_PATH -checks=-*,bugprone-*,clang-*,cppcoreguidelines-*,modernize-* -export-fixes build/yamls this gives me a bunch of moc_* complaints, but also complaints on my actual code. the moc_* complaints seem to be clang-tidy's complaints about Qt itself, so i filter those out.

could we please "unpin" this thread? quite a few things mentioned here are not relevant anymore, and the prominent place has a tendency to end up as a dumping ground for not-so-related issues.

@A123 said in New Errors when moving C++ code to QT Creator: its been used by others for years and it worked perfectly AFAIK with gcc and clang before I started using qtcreator which complained. Here's my guess: Previously, the assert() macro was disabled. This caused the illegal code to be effectively "commented out", so the compiler didn't detect it. After the migration, the assert() macro was no longer disabled, so the compiler now sees the bad code and (correctly) complains. See http://www.cplusplus.com/reference/cassert/assert/. You could make your code work again by defining the NDEBUG macro, but be careful: This will disable all assert()s which might cause other errors to go undetected. P.S. The compiler is the one that complained, not Qt Creator.

@BINALECTRUM said in Android build and deploy. 64bit, Clang, new app store developer console rules [2018 & 2019]: Is Qt going more in embedded/car side and just slowly drops Android/mobile platform? In Roadmap 2018 there is nothing new about mobile platform. i heavily doubt that. I guess the reason is more because Qt runs more or less stable on Android. There are no bigger features which need to be implemented, mostly bug fixing. What is your move Qt team on new app store rules in developer console: minimal platform-26 in August 2018 and 64-bit apk in 2019? Some new changes in build and deploy area? i asked this at the beginning of the year, but unfortunately haven't received an answer.

Did you install Xcode 8 ? Your other error comes from the fact that you are calling xcodebuild in the folder where it's located and not where a Xcode project can be found.

@SGaist Thank you.

Yes, I'm newbie in C++ and didn't know the problem with different libraries and compilers. Now it is clear. Thank you very much!

@SGaist Thanks! I'll waiting for next release!