@Christian-Ehrlicher
Got it working by myself now, but thanks anyhow for the quick reply.

The problem was that i called cmake from within the source not the build dir so it ran cmake for a fresh new build that wasn't already setup from within Qtcreator and did not know where to search for Qt stuff.

This is my script now:

cd C:\Build\myQtApp\build_r cmake -S Y:/ -B C:/Build/myQtApp/build_r "-DBUILD_TYPE_1:BOOL=ON" "-DBUILD_TYPE_2:BOOL=ON" cmake --build C:/Build/myQtApp/build_r --target all -j2 ... cmake -S Y:/ -B C:/Build/myQtApp/build_r "-DBUILD_TYPE_1:BOOL=OFF" "-DBUILD_TYPE_2:BOOL=ON" cmake --build C:/Build/myQtApp/build_r --target all -j2

The boolean parameters BUILD_TYPE_1 and so on are used inside cmake to add a preprocessor defines that are then used to switch between different build configurations just in case anybody wants to know.

In cmake:

if(BUILD_TYPE_1) message(STATUS "Build Type: Type 1") add_definitions(-DBUILD_TYPE_1) endif()

in c++

#ifdef BUILD_TYPE_1 ... #endif

@ADR_PT you may want to start using QSerialPort the asynchronous (non-blocking) approach, by using signals & slots.
Take a look at the serial terminal example

@galb1994
I believe everything of mine in Creator is on whatever the defaults are. I do assume you are Linux and not Win/Mac? I will be on whatever Creator comes with Ubuntu 20.04 apt-get (unless I fetch it myself, I forget).

Adding to @JKSH, the qml option expects the path to the files in your project sources so it can parse them to pull all the required dependencies.

@Amirhos
Unfortunately this is difficult, especially under Windows. If, for whatever reason, the third-party app is buffering its output at its own side then you cannot force it down the pipe to your parent, it depends how the code is written at their side....

@SGaist Thank you, this has solved my issue!! :D

@cstevenson Please also connect a slot to https://doc.qt.io/qt-5/qprocess.html#errorOccurred
The process is probably not running when you call write().

Hi and welcome to devnet,

To add to @mrjj :

1) qmake -project "QT += widgets" 2) qmake 3) make

The first one will create a project with the required Qt module for widgets.
The second will create the Makefile.
The third trigger the compilation.

Can you share the QProcess code you have written to execute the script ?

@mrjj It seems the /silent option doesn't exist in the pre-built binary. But I think I can create a controller script in order to control the gui installer by the script.

Thank you !