Qt creator terminal asking for user input
-
At least I have not seen such option. You can try running qmake from commandline itself and try
-
At least I have not seen such option. You can try running qmake from commandline itself and try
@dheerendra yes, but I'm hoping to make it user friendly for my colleagues. we have one machine that will pop up an external command line and allows user input. None of the other's do, and I can't figure out why.
-
@dheerendra yes, but I'm hoping to make it user friendly for my colleagues. we have one machine that will pop up an external command line and allows user input. None of the other's do, and I can't figure out why.
@graniteDev which input is that?
-
@graniteDev which input is that?
@aha_1980 part of our build requires running an external script that requires user input for it's operation.
-
Hi,
How are you requesting the input currently ?
-
@SGaist It's just a script that gets called as part of the build process to make sure all of our soup repos are correctly downloaded and of the right version. It requires user authentication though.
On one of our systems it works just right, the script window pops up in it's own cmd window (this is on Windows 10) and then the user can enter their credentials, the script does it's checking, and then closes and the build continues.
However on the rest of our systems, the external window doesn't open, instead the script runs inside the QtCreator console which does not allow for user input. This stops the build process because it just sits there waiting for user input that it can't receive.
The only solution I currently have is to clone this one working system. This has worked, the clones of this system behave the same way, but it's not an answer. What I need is to know how to invoke this behavior of opening an external command window, on purpose. Otherwise future modification to this "master" system could inadvertently kill this functionality and I'll have no way of getting it back.
-
@SGaist It's just a script that gets called as part of the build process to make sure all of our soup repos are correctly downloaded and of the right version. It requires user authentication though.
On one of our systems it works just right, the script window pops up in it's own cmd window (this is on Windows 10) and then the user can enter their credentials, the script does it's checking, and then closes and the build continues.
However on the rest of our systems, the external window doesn't open, instead the script runs inside the QtCreator console which does not allow for user input. This stops the build process because it just sits there waiting for user input that it can't receive.
The only solution I currently have is to clone this one working system. This has worked, the clones of this system behave the same way, but it's not an answer. What I need is to know how to invoke this behavior of opening an external command window, on purpose. Otherwise future modification to this "master" system could inadvertently kill this functionality and I'll have no way of getting it back.
@graniteDev I think this is pure luck that the command window pops up.
I also think, this is no official/recommended way to set up the project. The usual way is to provide these parameters as
qmakeormakearguments, or to set them via an environment variable. -
@graniteDev I think this is pure luck that the command window pops up.
I also think, this is no official/recommended way to set up the project. The usual way is to provide these parameters as
qmakeormakearguments, or to set them via an environment variable.@aha_1980 It may not be the official way, but it is the way we must do it. And since the window can pop up, and cloned systems behave the same way, it must be a setting somewhere, but I and my colleagues have yet to find it.
-
Did you check whether you had a difference of configuration of Qt Creator or the project itself between the working machine and the others ?
-
Did you check whether you had a difference of configuration of Qt Creator or the project itself between the working machine and the others ?
@SGaist We've gone over QtCreator with a fine tooth comb. They are identical. It's project independent since it's qmake command calling an external script.
-
And from a project point of view ? Thinking about the "Run in terminal" parameter.
-
@SGaist I think I know what you are getting at. This is a corporate project, cloned from the same repo on all machines involved. Some of the sub projects are console, some are widget applications, and one is qml. This script is called from qmake during the build of the whole project, not any one sub project.
-
Would it be possible to share a minimal project that shows that behaviour ?
