Unsolved Qt Creator 3.5: Remote execution broken?
I'm trying debug my program on a remote linux server from within Qt creator.
The device works without any problems; the test runs through (the test-button at options>devices), I can see the processes (at the same place) and the deployment via sftp works (when pressing the big green play button :)).
But it doesn't work to run the program then. Neither via "Custom Executable" nor via the "<project name>" run configuration. A "Run ... on Linux Device" window appears in Application Output but just stays empty and the executable is not running on the remote host.
The project is a simple "Hello World"
Thanks for your help!
Hi and welcome to devnet,
You have to be more specific otherwise it's pretty much Crystal Ball debugging. What are you trying to connect to ? What error are you getting ?
@SGaist Thanks for the welcome and swift reply. Indeed I accidentally hit Submit in the middle of a sentence, I added more information now.
What is the test that runs correctly ?
I'm talking about the "Test"-button under Options > Devices.
Unfortunately I can only answer rate-limited because of low reputation... I'll put more details in the description above.
So you followed this guide and related links to setup your Qt Creator and run your application ?
@SGaist yes, exactly.
The next question might sound silly but do you have Qt properly installed on your target ?
@SGaist It's not a silly question at all! There is indeed no qt installed on the target, but as I'm starting a simple c++ hello world without any qt-stuff involved I thought i wouldn't need that. Also there is the option to say "none" for qt in Options>devices...
So does Qt creator use some qt stuff to start the executable?
Thank you very much for all your help so far already!
SGaist Lifetime Qt Champion last edited by SGaist
No it should not. AFAIR it uses ssh to connect to your device and handle everything from there. What is your hello world doing ?
You're welcome :)
@SGaist this is the program:
running it manually works as expected (both locally and on the target)
And you don't get anything written to that file ?
That's correct. :)