Aha! Thanks @jeremy_k
The final answer was qt.*.debug=false. I now see the qDebug() warnings, but not all the annoyinbg QT logs.
So my qtlogging.ini looks like

Thanks again, both of you!

Thank you for the information.

@James-Gallegos It works, Thanks

I have started using Squish relatively recently. It's hard work to get something working robustly but I think I am getting there with the main part of my QML application. One aspect that is causing difficulty is the file dialogs that we use in a few places.

On Windows, I am using FileDialog from QtQuick.Dialogs 1.3, which resolves to a system file dialog. I can't get reliable identifiers for buttons and so on (they seem to shift from run to run) and picking files is very fragile. I can't examine the UI as programmatically as I can in the pure QML code and have to resort to coordinate-based picking of files. This is fragile and makes it harder to factor out common script fragments as I have done for other aspects of our GUI. For some reason I don't recall now I couldn't get the dialog to work by typing in the file name in the text box. It has basically been one problem after another for what is really a small part of our workflow.

I am wondering if anyone has any tips for dealing with file dialogs under Squish. My current thinking is that there isn't actually a lot of point in testing what is essentially a system dialog that I have no control over, so I am considering having a "running under Squish" mode for my application that will just pop up basic text input dialogs, written in pure QML, in place of any file dialogs. Does this sound like a reasonable approach?

Hello friends, it has been 1 week since I applied for the training package but I still haven't received a response. What should I do?

I encountered the same problem.

Wayland-scanner client-header < /home/lsqtpi/raspi/qtsrc/qt-everywhere-src-5.13.2/qtwayland/config.tests/wayland_scanner/scanner-test.xml > wayland-scanner-test-client-protocol.h
When I manually executed the above command from the console,
it displayed a message to install the following library.

sudo apt install libwayland-bin

@Lee_Corl Please read the link I gave you.
On Windows you link *.lib files like:

And please post text, not pictures...

I had the same goal. I used Docker (Windows 10) and CROPS to run Debian container on Win10 to cross compile.
With a hefty machine (8-12 cores, 32 GB RAM) I am able to cross compile from Win10 to the target (Toradex Colibri) pretty easily

https://docs.yoctoproject.org/dev-manual/start.html#setting-up-to-use-cross-platforms-crops