VAR-SOM-MX6 B2QT: Difference between revisions

From Variscite Wiki
(Created page with "=About Boot to Qt= Boot to Qt is a light-weight, Qt-optimized, full software stack for embedded Linux systems that is installed into the actual target device. This is done by...")
 
Line 1: Line 1:
=About Boot to Qt=
=About Boot to Qt=


Boot to Qt is a light-weight, Qt-optimized, full software stack for embedded Linux systems that is installed into the actual target device. This is done by flashing the device's memory card or internal memory directly with a pre-built image that comes with the online installer. See the Installation Guide for details.
Boot to Qt is a light-weight, Qt-optimized, full software stack for embedded Linux systems that is installed into the actual target device.


Boot to Qt is ideal for the following use cases:
Tthe stack can be customized to production with Build-Your-Own-Stack tooling, including proprietary Yocto Project recipes.
 
* Evaluating Qt on real embedded environment using one of the provided reference images.
* Getting the embedded development environment up and running in no time. Later, the stack can be customized to production with Build-Your-Own-Stack tooling, including proprietary Yocto Project recipes.


[[File:B2QTstack.png]]
[[File:B2QTstack.png]]

Revision as of 09:20, 30 June 2017

About Boot to Qt

Boot to Qt is a light-weight, Qt-optimized, full software stack for embedded Linux systems that is installed into the actual target device.

Tthe stack can be customized to production with Build-Your-Own-Stack tooling, including proprietary Yocto Project recipes.

B2QTstack.png

The full B2QT documentation is available at Qt for Device Creation official page.

Requirements

You should be familiar with the Yocto tools and the concept of recipes. For more information, see Yocto Project documentation.

To get started, you need the following:

  • Install the Boot to Qt source packages. You can find these by running the MaintenanceTool application located in the Qt for Device Creation installation directory and selecting Package Manager. The Yocto meta layer package contains the additional recipes required to make the image compatible with Boot to Qt.
  • Install the dependencies for the Yocto tools. In Ubuntu, the following packages are required:
sudo apt-get install gawk curl git-core diffstat unzip p7zip texinfo \
gcc-multilib build-essential chrpath libsdl1.2-dev xterm gperf bison \
g++-multilib

Setting Up Yocto Build Environment

Run the setup script that initializes the Yocto environment. Using Variscite VAR-SOM-MX6 as an example:

mkdir ~/var-b2qt
cd ~/var-b2qt
git clone https://github.com/vkonstantins/meta-variscite-boot2qt -b morty-var01
cd meta-variscite-boot2qt
./b2qt-init-build-env init --device var-som-mx6

b2qt-init-build-env has the following additional command line options:

  • list-devices: show all supported devices that can be used for a Boot to Qt build
  • mirror: create a local mirror of the yocto repositories. This enables you to use the same repository downloads for multiple build environments, when initializing with init --reference <mirror path>.

For all command line options, see:

./b2qt-init-build-env help

Building the Image and Toolchain

After the Yocto environment is set up, you need to configure the build environment for your target device:

export MACHINE=var-som-mx6
source ./setup-environment.sh

The following table lists the MACHINE values for our reference platforms:

SoMs & boards target
VAR-SOM-SOLO/DUAL/MX6, DART-MX6 and related board configurations var-som-mx6
DART-6UL and related board configurations imx6ul-var-dart
VAR-SOM-MX7 and related board configurations imx7-var-som

Yocto recipes for Boot to Qt for embedded Linux have two main targets to build: The target image, and the external toolchain that can be used with Qt Creator for building Qt applications.

bitbake b2qt-embedded-qt5-image
bitbake meta-toolchain-b2qt-embedded-qt5-sdk

The target rootfs image is located in the

~/var-b2qt/meta-variscite-boot2qt/<target>/tmp/deploy/images/<target>/b2qt-embedded-qt5-image-<target>.img

and the new toolchain is in

~/var-b2qt/meta-variscite-boot2qt/<target>/tmp/deploy/sdk/b2qt-x86_64-meta-toolchain-b2qt-embedded-qt5-sdk-<target>.sh