title: Qt Creator remote debugging
body: <p>I have an application that I run on an Embedded Linux device.
  In Eclipse, I can run remote debugging using the <code>eclipse-cdt-launch-remote</code> plugin where I point a binary to run, and where to put it on the device with some environment variables to be exported before running the application.
  The application is a <code>C++</code> application with a custom Makefile for building the application as an <code>ELF</code> file.</p>
  
  <p>The application is deployed on the device via <code>SSH</code>, using login with user and password. And then, I can debug from Eclipse using stepping and so on.
  (I am also using the MentorGraphics crosscompiler for arm-none-linux-gnueabi-2014.05)</p>
  
  <p>My question is: <strong>How do I mimic the same functionality in Qt Creator since I like coding with Qt Creator more than coding with Eclipse?</strong> 
  I know that an easy fix would be to code in Qt Creator, and then debug using Eclipse, but I really want to debug using Qt Creator.</p>
  
  <ul>
  <li>Edit: Solved it by hours of testing and reading up on the Qt Creator
  IDE.
  
  <ol>
  <li>Imported my project that was an Makefile project.</li>
  <li>Then I went in to Options under Tools and added my Device that used SSH.</li>
  <li>After that I added a debugger, I used gdb-multiarch since the one provided in the prebuilt toolchain binary did not support python.</li>
  <li>Then I added my custom toolchain pointing the compiler path to the toolchains binary g++. And set the ABI to
  arm-linux-generic-elf-32bit. Although I dont actually see the
  compiler settings being used during debug.</li>
  <li>I created a new kit using my Device, Debugger, and Compiler. And set device type to Generic Linux Device. Pointing to my sysroot that
  I extracted when using buildroot for the filesystem. These were the
  only options I set in the kit.</li>
  <li>Closed the options menu, and went into Projects where I added my new kit</li>
  <li>Changed the build settings and set the build directory and build steps for the application.</li>
  <li>Changed the run settings to use some custom commands, like moving the newly built .elf application to target. And then I set where the
  local executable was and where the remote executable was. The remote
  executable is the one I moved to the target using custom command from
  host.</li>
  <li>Voila! I could now run remote debugging on my target from Qt Creator.</li>
  </ol></li>
  </ul>