4

I'm trying since days to write and develop programs on my host pc (Ubuntu 64bit) using qt-creator for my beaglebone and raspberry pi devices. I looked for 'qt-creator cross compile beagle, raspberry etc...' and it leads me to hundred of links and tutorial on how to compile qt-creator for my target plattform. But seriously, that not my idea. All what I want is to simply use my pc for developing my programs and lately deploy them to the remote device.

So first of all a noob question: Is something wrong with my idea? Should I really compile the source of qt for beaglebone or raspberry on my pc for writing programs which lately should be run on that devices????

I will not compile qt-creator again for another plattform, so I don't know how to find the right way. A lot of informations on internet are misleading.

So after many hours spend look for the right information I come up with the following procedure:

first I installed a arm-gnu toolchain on my 64bit Ubuntu.

sudo apt-get install build-essential libc6-armhf-cross libc6-dev-armhf-cross binutils-arm-linux-gnueabihf linux-libc-dev-armhf-cross libstdc++6-armhf-cross gcc-4.8-arm-linux-gnueabihf g++-4.8-arm-linux-gnueabihf

then I installed qt-creator from the repository on my Ubuntu:

sudo apt-get install qtcreator

I tried to configure to use qt for compiling my projects using the toolchain for arm (see following pictures)

enter image description here

and here:

enter image description here

but it seems that qt-creator doesn't recognize the new kit when I start a new project:

enter image description here

Now: I m really confused, I could think that the problem is related to qt, but I m not sure, whether the way of thinking, that I can compile on ubuntu 64bit and then run my application on the remote device is right or not.

For this reason it would be nice if you can answer the question above.

UPDATE: What happen if I add a QT-Version in my Kit???

It happens that the gnueabi compiler conflicts with that options and the following problem arises:

enter image description here

I would like to say again that I don't need to use qt-library or something like that on my remote device. I need just to use the qt-IDE as IDE for my projects (mainly c or c++ plain projects)

Dave
  • 349
  • 4
  • 22
  • "Qt version: None". So you don't have a x-compiled build of Qt? – peppe Sep 26 '15 at 20:39
  • What do you mean? I what to use qt-creator as a IDE for my projects but I don't need to use qt-library or something like that. Maybe I don't understand you right.... – Dave Sep 26 '15 at 20:42
  • Oh, sorry, I thought you wanted to also use Qt for your target application. If you apply the changes in the Build&Run pane, is the BB kit marked with a red flag or somesuch (indicating a misconfigured kit)? – peppe Sep 26 '15 at 20:44
  • yeah...I updated the question. You can take a look at the screen shot – Dave Sep 26 '15 at 20:51
  • I don't know the answer, I'm sorry. May I suggest you raise this question on the qt-creator mailing list? I'm not sure if a suitable x-compiled Qt version is needed at all times, but I fear so. Without such a version, Creator is practically crippled, as I think it knows how to deploy only when using a qmake-based project; and you have no qmake... – peppe Sep 26 '15 at 20:55
  • I have not yet used but Yocto project supports building sdk for Qt and supports building it for beaglebone black. I have built it but not yet used it. I will try and let you know. – ART Sep 28 '15 at 07:49

3 Answers3

0

You need a complete toolchain

A toolchain is just a name for a group of things:

  • Compiler for the target platform (or cross compiler in your case)
  • Sysroot: An image of the filesystem in the target platform
  • A cross compiling qmake
  • QtCreator and the kit

You are lacking a cross compiling qmake. Please see my answer at this other post.

Furthermore, you need a toolchain for the Pi, and another toolchain for the Beagle.

Community
  • 1
  • 1
Ariel M.
  • 896
  • 8
  • 24
0

It looks like before the update in the question, you didn't even have a valid kit, so there was nothing the IDE could do. You need to create a kit, and set Qt Version to None - because whatever Qt version you have installed is not for the ARM target. So, as long as it'll be none, it should work then, assuming that you have installed a full ARM toolchain for the target, including the Linux-specific bits - since you're not building a bare-bones application, but an application that will run on Linux.

When creating a new project, make sure to select Non-Qt Project, either C or C++, and choose the CMake build system (not qmake or qbs).

To test this out, start with creating a kit for your host platform, without selecting a Qt version (set it to None), and make sure you can create a simple C project and build it (choose proper compilers etc). Once you have done that, you should have an idea how to proceed with building for your ARM Linux targets. It really shouldn't be problematic at all (it all "just works" in my experience), so you probably didn't install something major (related to the target toolchain, nothing to do with Qt nor Qt Creator).

Kuba hasn't forgotten Monica
  • 95,931
  • 16
  • 151
  • 313
-1

In Derek Molloy's tutorial for the Beaglebone on this subject, he mentions at around minute 18 that installing QT directly through the command sudo apt-get install qtcreator, won't install all the features of the QT app.

Try downloading QT directly from Qt site.

Luis Mendez
  • 1