When I did that, (for a arm linux,but still...) I used a generic process and called the original Makefile. You might want to make a Makefile wrapper if you need a different build system. I even wrapped the run command configuration to ssh to the remote arm device and execute the new application (using a small shell script wrapper).
I did not find the time to have remote GDB working, but I understand this is possible. I started using a dummy pro file, but found it not adequate as compilation problems where harder to find. Using a generic Makefile project you can press control+b and find the problems the compiler spits. You will also need to adjust the include directories and defines. This is trivial and you will find how to do it. On Mon, May 7, 2012 at 10:40 PM, Jason H <[email protected]> wrote: > I have a legacy project that I hope to get running and use QtCreator for. > > This is all C code at the moment but I hope to still be able to use qmake > and creator. I also have a USB tap for debugging, that I was hoping I could > get using with Creator. > > Is there some kind of step-by-step manual to walk me through how to get it > going? > > Thanks. > > > _______________________________________________ > Qt-creator mailing list > [email protected] > http://lists.qt-project.org/mailman/listinfo/qt-creator > >
_______________________________________________ Qt-creator mailing list [email protected] http://lists.qt-project.org/mailman/listinfo/qt-creator
