I have an application that I run on an embedded Linux device. In Eclipse, I can start remote debugging using a plugin eclipse-cdt-launch-remotewhere I specify the executable for the binary code and where it can be placed on the device with some environment variables that must be exported before the application starts. An application is an application C++with a custom Makefile to create an application as a file ELF.
The application is deployed to the device through SSH, using the username and password. And then, I can debug Eclipse with stepping and so on. (I also use the MentorGraphics cross-compiler for arm-none-linux-gnueabi-2014.05)
My question is: How do I simulate the same functionality in Qt Creator, since I prefer encoding with Qt Creator more than encoding with Eclipse? I know that an easy fix will be to code in Qt Creator and then debug using Eclipse, but I really want to debug it using Qt Creator.
- Edit: Solved it for hours of testing and reading on the Qt Creator IDE.
- Imported a project that was a Makefile project.
- Then I went into the “Options” under the “Tools” section and added my device using SSH.
- After that I added a debugger, I used gdb-multiarch, since the one that was specified in the prebuilt binary toolchain binding did not support python.
- Then I added my special binding, indicating the compiler path to the g ++ toolchains binary. And install ABI for arm-linux-generic-elf-32bit. Although I really don't see the compiler options used during debugging.
- I created a new set using my device, debugger and compiler. And install the device type on the universal Linux device. Pointing to my I extracted when using buildroot for the file system. These were only the parameters that I set in the kit.
- I closed the options menu and went to Projects, where I added my new kit
- The assembly parameters are changed and the assembly directory and assembly steps for the application are specified.
- , , , .elf. ,
.
- ,
.
- Voila! Qt Creator.