Skip to content
  • 0 Votes
    2 Posts
    3k Views
    A

    Hi,

    I have been starting development using QT a few weeks ago and encountered a similar problem. Everything was fine, compiling the apps and deploying to the PI using QT Creator without issues. But as soon as I started the app (or wanted to debug) the app died with a Segfault.

    After some hours, I noticed that libts on Jessie has been quite old. I re-installed Jessie-Lite and compiled libts on my own, directly from the GitHub repository here: lbts GitHub Repo .

    Afterwards I simply followed the tutorial to cross-compile QT5 like documented in this tutorial: RaspberryPi2EGLFS

    Basically I followed each step within the tutorial and the only thing I did not do, was to install any libts related packages (just check the apt-get install commands in the tutorial and don't install the libts related packages).

    I know, the thread is quite old, but maybe someone will look it up.

  • 0 Votes
    8 Posts
    4k Views
    Pablo J. RoginaP

    @Jaykovs I don't know any guide for specific platform, but I'd follow some of the guides to cross-compile Qt (mainly for Raspberry Pi) that can help you as a reference. BTW, what device is the one you're using?

    Examples:
    http://forum.qt.io/topic/56049/setting-up-cross-compiler-rasp-pi/10
    http://processors.wiki.ti.com/index.php/Building_Qt#Building_Qt.C2.A0
    http://doc.qt.io/QtEnterpriseEmbedded/qtee-custom-embedded-linux-image.html

  • 1 Votes
    6 Posts
    5k Views
    KevinMQtK

    @charlycoste said in No GNU licence for device creation?:

    That's what I understand too... But where are we supposed to find Qt open-source version for Device Creation?
    On the Qt for Device Creation page, you can only request a Trial.

    Qt open-source for Device Creation does not exist. There's only one Qt open-source version. Qt for Device Creation is not really that unique. It's just the normal Qt for Application Development with additional modules, software stacks (e.g. Boot to Qt & Qt Automotive Suite) and pre-built images to make it easier to develop and deploy on Embedded devices. So this means you'll have to download the open-source version and configure it to cross-compile on the board (target device) you want. For beginners, I recommend starting out with Raspberry Pi. Here are a few resources you can use.
    https://mechatronicsblog.com/cross-compile-and-deploy-qt-5-12-for-raspberry-pi/
    https://medium.com/@amirmann/how-to-cross-compile-qt-for-raspberry-pi-3-on-linux-ubuntu-for-beginners-75acf2a078c

    Qt for Device Creation is already pre-configured and has pre-built images for several target devices. Not to mention it uses the commercial license so you don't have to release the source code. It also comes with support if you need it. But for a hobby project, I think the open-source version is okay if you're prepared to set up everything by yourself.

    Oh! Almost forgot. Qt Extended/Qtopia (a subset of Qt Embedded- I think this was also GPL at one point) was once released under the GPL license but it was discontinued back in 2009 when Nokia owned Qt. It was designed for embedded Linux-based mobile devices like the Greenphone or the Neo FreeRunner. After the discontinuation, it was forked in QtMoko but I don't think it's being developed anymore.