[Qt-creator] BareMetal Target Plugin
daniel.teske at digia.com
Wed Aug 14 13:16:59 CEST 2013
On Wednesday 14 Aug 2013 13:00:15 you wrote:
> 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.
The ony requirements are, and I repeat myself here:
- Various files in the mkspec directory, those are needed by qmake.
- That the bin directory exists (which given that the qmake binary is in it is
a rather easy requirement.
- That the include directory exists, but that can be empty. That is the only
one that is in addtion to what would work on the command line. We check that
directory, since it is quite common for those who compile qt from source to
not do a -prefix . build / not install.
> 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.
That's wrong, there is no need to have a libQtCore.so.
More information about the Qt-creator