Qt Creator and other tools

Does anyone have an idea? I want to debug a binary which is started over a start script. Debugging the binary directly works. Also if i set the start script to not start the binary directly, but add "gdbserver :7777 /mypath/helloworld", I can connect to the debugger using the "Debug -> Start Debugging -> Connect To Remote" and fill out the details there. However, this disrupts my workflow and needs manual patching. Is it somehow possible to have a start script as alternate executable in the project settings AND being able to remote debug it?

@SimonSchroeder @KH-219Design Thank you. Answers located here.

Why not use the example from the documentation to implement your tests since you want to use the QtTest module ?

Hi and welcome to devnet, Are you looking for something like the new Qt/.NET module ?

Hi and welcome to devnet, From the looks of it, you did not install g++. To get your system ready for development, check this documentation page.

That shouldn't happen. Consider creating a bug report. Or provide the information that's usually requested here. See https://wiki.qt.io/Qt_Build_System_Glossary#Reporting_build_system_issues for details.

@PolywickStudio hi, By default, the build is dynamic so you should not need that option. That said, it looks like either the documentation is wrong or the script. I would suggest that you check the bug report system to see if there's already something about it and if not, please open a new ticket.

Qt Creator 11 will add the source files to the CMakeLists.txt. See below an example of a Widgets application: [image: qtcreator11-widgetsapp.gif]

I had the exact same problem on Fedora 38. I found a workaround that solves this problem for me. Just wrote a shell script wrapper around the qt program, like so: #!/usr/bin/env bash QT_QPA_PLATFORM=wayland ~/qtcreator-9.0.2/bin/qtcreator So setting the QT_QPA_PLATFORM environment variable to wayland does the trick!

@SGaist I had the same issue but 'qmake -project -recursive src' still didn't work, so I simply ran 'qmake -project' with the old qt4 qmake and this worked for me.

@ZINE If you use no_keywords then you have to use macros instead of signals/slots "key"-words like explained here: https://doc.qt.io/qt-6/signalsandslots.html

i have the same problem ... if you have education license you can sign in to your qt account and download qt-license file and save it to home directory this worked for me.

First, make sure you have all the necessary dependencies installed on your system. You can use the apt package manager to install them. Check the Qt documentation for the specific dependencies required for your version of Qt. Once you have the dependencies in place, download the source code for Qt and extract it to a directory of your choice. Then, open a terminal and navigate to the extracted directory. Next, you'll need to configure Qt with the appropriate options for static building. The configure script provides several flags to enable static building, such as -static and -static-runtime. You may also need to specify the path to the static version of any external libraries you want to include. After configuring, run make to start the build process. This may take a while, depending on the speed of your system. employee monitoring software

It works when I select libtorch that supports cxxabi and delete the define in the .pro file: #QMAKE_CXXFLAGS += -DGLIBCXX_USE_CXX11_ABI=0. Thank you @Christian-Ehrlicher.

@DarkSky And... I installed PySide6 on WSL2, but it doesn't run there either, missing libxkbcommon.so.0, which BTW https://www.x.org/releases/individual/lib/ does not have listed.