Qt Creator and other tools

Well, as silly as it may sound: select the Qt 5 installation you have from brew. If you don't have it, go to the Qt versions tab and set it up there. Then come back to the kit page and chose it there.

I was having the same problem, but for me has worked to disable the Clang code model and restarting Qt.

I solved it by creating qt creator plugin that contains qt_set_sequence_auto_mnemonic(false).

@aha_1980 Thanks for your hint. cout still doesn't work correctly, even when not mixed with qDebug(), see picture attached [image: 93752b46-c28d-45b0-948d-ba63e3dbda50.png]

@Adam-Badura Though this thread is very old, I actually ran across it when trying to define a custom qmake rcc compiler for pyrcc5 which compiles resources to python byte code in PyQt5. The problem is that I wanted to use the target.depend_command to list out the resource files needed for the resource compiler. This is crucial for editing qml files and having the change picked up in a call to make. rcc -list works perfectly for this. For the record, here is my custom compiler: pyrcc5.input = RESOURCES pyrcc5.output = qrc_${QMAKE_FILE_BASE}.py pyrcc5.dependency_type = TYPE_RCC pyrcc5.depend_command = rcc -list ${QMAKE_FILE_NAME} pyrcc5.CONFIG = no_link target_predeps dep_lines add_inputs_as_makefile_deps pyrcc5.commands = pyrcc5 ${QMAKE_FILE_NAME} -o ${QMAKE_FILE_OUT} QMAKE_EXTRA_COMPILERS += pyrcc5 (And here is my custom pyuic5 compiler:) pyuic5.input = FORMS pyuic5.output = ${QMAKE_FILE_BASE}_form.py pyuic5.dependency_type = TYPE_UI pyuic5.CONFIG = no_link target_predeps dep_lines pyuic5.commands = pyuic5 ${QMAKE_FILE_NAME} -o ${QMAKE_FILE_OUT} pyuic5.variable_out = GENERATED_FILES pyuic5.name = PyUIC5 ${QMAKE_FILE_IN} QMAKE_EXTRA_COMPILERS += pyuic5

Due to other problems, I wiped out my Qt installation and re-installed. It now sees 5.14.2. I do believe I managed to get something screwed up in my Qt directory. Anyway, this problem went away. Thanks for looking...

@wokerjrvm How is your question related to the original question in this thread? Please open your own thread and ask there.

I had this same issue using QtCreator 4.11.2 in MSYS2, but trying to use the MSYS2 GCC (package msys/gcc) instead of the default mingw64/gcc. If I select (auto-detected) MSYS2 GCC as the compiler in the kit configuration, then the inline compilation messages indicate that stdio.h cannot be found, and under Tools > C++ > Inspect C++ Code Model, the field "BuiltinPath", which is supposed to have the path to system includes, shows as blank. I partially fixed this, after reading this thread, by setting the kit's sysroot to be the path of my MSYS2 installation. Setting sysroot to F:\Prog\msys64 caused the Clang Code Model's BuiltinPath to be detected correctly as F:/Prog/msys64/usr/include . This causes #include <stdio.h> to be handled correctly, but #include <stddef.h> still fails. Because that file is in F:\Prog\msys64\usr\lib\gcc\x86_64-pc-msys\9.3.0\include . As a workaround I added F:\Prog\msys64\usr\lib\gcc\x86_64-pc-msys\9.3.0\ to the INCLUDEPATH for Qmake, or the includes list for external project. But this is not really a desirable solution. Furthermore, setting this sysroot causes debugging with GDB to fail as it can no longer find C:\Windows\system32 for DLLs that the binary depends on. So in the end I reverted the sysroot to blank and also added F:\Prog\msys64\usr\include to INCLUDEPATH. Is there any way to manually configure what shows up under BuiltinPath so I can put the right paths there? Should it be considered a bug that qtcreator does not correctly set BuiltinPath without manual intervention?

Do you wish to be prompted for your password each time? I have set up so that my ~/.ssh has the necessary, so I don't need to get prompted each time.

@JonB You're right, thanks! :)

Personally I would open a command prompt and use something like that: lupdate.exe "MyProjDir" -ts "MyProjDir\myapp_fr_CH.ts" "MyProjDir\myapp_pt_BR.ts" "MyProjDir\myapp_ja.ts" -no-obsolete Thus all files containing strings to translate in my project directory will be updated in my .ts files (in this case the FR_CH, PT_BR and JP languages), but all the strings which are not included in my project will be discarded from the .tr files by the -no-obsolete option. And only then, I would call the lresease tool.

The problem persists. No solution found so far.

@mrjj I get it. Thx!

Hi @tmk_rudnicki, are your tests in a header file? What happens if you put them in a cpp file? Regards

For clarification: does this occur only with one particular project, or with any project?

@smamran Just to clarify: this is user forum, not Qt development team. If you want to contact Qt developers use their mailing list (https://lists.qt-project.org/listinfo/development), if you want to file a bug report use Qt bug tracker (https://bugreports.qt.io/secure/Dashboard.jspa).

I got CXError_Failure when libclang couldn't handle one of the compiler arguments in compile_commands.json. See QTCREATORBUG-22063.