[Qt-creator] BareMetal Target Plugin

Poenitz Andre Andre.Poenitz at digia.com
Wed Aug 14 13:00:15 CEST 2013

Daniel wrote:
> Tim wrote:
> > If i may deploy for a remote linux target which unfortunatly has no QT
> > installed. I have a working qt installation and a working qmake (otherwise
> > the project build with qmake would fail earlier). This is used to make a
> > cross build without QT for the target. Currently all pieces in qtcreator
> > are there but it can't be configured as the selection dialog is greyed out
> > in the project configuration because the kit has no qt assigned. As qmake
> > is used as a build tool with "config -= qt" there is no qt needed on the
> > target device and so it should not be greyed out in this special case.
> But you still need to tell creator which qmake you want to use, which is done
> via the qt version. That does not in any way affect whether the resulting
> executable depends on qt.

The problem is that just pointing to a qmake binary is not enough as Creator
runs a couple of sanity checks to ensure the associated Qt build is "usable".
This is simply "too much" in this particular case.

It is possible to trick Creator into believing that "all is well" by creating 
a dummy libQtCore.so matching the target architecture and copying parts
of a real Qt's mkspec directory, but that's clearly a hack.

However, it shows that the setup works, and I think it's a use case that's
worth supporting properly. It seems to be rather common to share code
between, say, a Qt based visualization application running on a desktop 
and some data acquisition process running on an embedded system 
without Qt. The request comes up  regularly, from different parties.


More information about the Qt-creator mailing list