GitLab

That's the first step to make the gdb/trk Adapter work with the otherwise
unmodified gdb engine. GdbProcessBase is inherited by GdbProcess and the
gdb/trk Adapter. In the GdbProcess case it's just a wrapper around a QProcess
running gdb, in the Adapter case it's the interface to the gdb process in the
whole rfomm/gdb/gdbserver combo.

evaluating a file (which might not exist) is a bit different than just
merging a (possibly empty) map ...

gdb as it starts asking questions afterwards.

Fixes a bug where the cmake plugin wasn't finding make, if the make
commands directory was added to path in the build environment.

For implementing mouse navigation in the QML editor.

void main()
{
{
}
int i;
}

Rationale: The concept of a "Qt Dir" is dead ever since Qt can be
installed. Specifying the qmake location otoh makes it possible to
unambigously detect all parts of a Qt installation.

Reviewed-By: hjk

Also makes the code a lot smaller.

If there are multiple files with the same name, then we try harder to
find the correct one. That is for jom and nmake we have a relative path
so we try to find a file which matches the relative path completly.
Instead of just comparing the last part.

Basic TRK/adapter communication now works using "rfcomm listen /dev/rfcomm0 1
&& ./adapter -f -v /dev/rfcomm0 127.0.0.1:3222 && ./cs-gdb"

This is wrapped up in a "runner" binary