1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
|
/****************************************************************************
**
** Copyright (C) 2014 Digia Plc
** All rights reserved.
** For any questions to Digia, please use the contact form at
** http://www.qt.io
**
** This file is part of Qt Enterprise Embedded.
**
** Licensees holding valid Qt Enterprise licenses may use this file in
** accordance with the Qt Enterprise License Agreement provided with the
** Software or, alternatively, in accordance with the terms contained in
** a written agreement between you and Digia.
**
** If you have questions regarding the use of this file, please use
** the contact form at http://www.qt.io
**
****************************************************************************/
/*!
\page qtee-custom-embedded-linux-image.html
\title Building Your Own Embedded Linux Image
\previouspage qtee-customization.html
\nextpage qtee-static-linking.html
\B2QL is built using the tools and resources from the \l {Yocto Project},
and is based on Yocto's reference distribution (\e Poky). You can
use the same tools to build custom \B2Q images, and have control over
which packages are included in the build and how the software stack
is configured.
\section2 Note About Support Services for Yocto Tools
By default, The Qt Company will only provide customer support for the Yocto
recipes on the reference platforms, as delivered with \SDK, and
setting up the development environment for them. Receiving support
for any other configuration requires a separate service agreement
between a customer and The Qt Company.
\section1 Requirements
You should be familiar with the Yocto tools and the concept of
\e {recipes}. For more information, see Yocto Project
\l{https://www.yoctoproject.org/documentation/current}{documentation}.
To get started, you need the following:
\list
\li Install the \B2Q \e source packages. You can
find these by running the \e MaintenanceTool application
located in the \SDK installation directory and selecting
\e {Package Manager}. The \e {Yocto meta layer} package
contains the additional recipes required to make the image
compatible with \B2Q.
\li Install the dependencies for the Yocto tools, build
scripts, and the Qt modules. In Ubuntu, the following
packages are required:
\badcode
sudo apt-get install gawk wget git-core diffstat unzip p7zip-full texinfo \
gcc-multilib build-essential chrpath libsdl1.2-dev xterm gperf bison curl \
udisks screen
\endcode
\endlist
\section1 Setting Up Yocto Build Environment
Run the setup script that initializes the Yocto environment. Using Freescale
SABRE SD i.MX6Quad as an example:
\badcode
cd <BuildDir>
<INSTALL_DIR>/5.5/Boot2Qt/sources/b2qt-yocto-meta/b2qt-init-build-env init --device imx6qsabresd
\endcode
\c b2qt-init-build-env has the following additional command line options:
\list
\li \c list-devices: show all supported devices that can be used for a \B2Q build
\li \c 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 \c{init --reference <mirror path>}.
\endlist
For all command line options, see:
\badcode
<INSTALL_DIR>/5.5/Boot2Qt/sources/b2qt-yocto-meta/b2qt-init-build-env help
\endcode
\section1 Building the Image and Toolchain
After the Yocto environment is set up, you need to configure the
build environment for your target device:
\badcode
export MACHINE=imx6qsabresd
source ./setup-environment.sh
\endcode
The following table lists the \c MACHINE values for our reference platforms:
\table
\header
\li Board
\li MACHINE value
\row
\li Raspberry Pi
\li raspberrypi
\row
\li Raspberry Pi 2
\li raspberrypi2
\row
\li BeagleBone Black
\li beaglebone
\row
\li Boundary Devices i.MX6 Boards
\li nitrogen6x
\row
\li Freescale SABRE SD i.MX6Quad
\li imx6qsabresd
\row
\li Freescale SABRE SD i.MX6Dual
\li imx6dlsabresd
\row
\li Toradex Apalis iMX6
\li apalis-imx6
\row
\li Toradex Colibri iMX6
\li colibri-imx6
\row
\li Toradex Colibri VF
\li colibri-vf
\row
\li SILICA ArchiTech Tibidabo
\li tibidabo
\row
\li Emulator
\li emulator
\endtable
Yocto recipes for \B2QL have two main targets to build: The target image,
and the external toolchain that is used for building the Qt framework and
applications.
\badcode
bitbake b2qt-embedded-image
bitbake meta-toolchain-b2qt-embedded-sdk
\endcode
The target rootfs image is located in the \c <YoctoBuildDir>/tmp/deploy/images/<target>/b2qt-embedded-image-<target>.tar.gz,
and the new toolchain is in \c <YoctoBuildDir>/tmp/deploy/sdk/b2qt-eglibc-x86_64-meta-toolchain-b2qt-embedded-sdk-<target-architecture>-toolchain-1.6.sh
\note The generated target image does not yet include Qt libraries,
you need to build Qt and add it into the image yourself.
\section1 Building Qt and Addons
\e {Build scripts} source package contains scripts that can be used to
build Qt and all additional Qt addons that are part of \B2QL image.
To setup build environment for your target hardware, run the initialization
script. For example:
\badcode
<INSTALL_DIR>/5.5/Boot2Qt/sources/b2qt-build-scripts/embedded-common/init_build_env.sh <INSTALL_DIR>/5.5/Boot2Qt/sources/b2qt-build-scripts/embedded-linux/config.imx6qsabresd
\endcode
\note You can use the same build directory for Qt and the Yocto image.
The toolchain and the target image are then used from the Yocto build directory.
You can use following scripts to build different parts of the \B2Q stack.
\badcode
./build_qt.sh
./build_extras.sh
./build_image.sh
\endcode
After \e {build_image.sh} has finished, you can write the updated image to your SD card:
\badcode
sudo ./deploy.sh /dev/<device_name>
\endcode
\section1 Configuring Qt Creator
After you have built the \B2Q stack, you must also set up Qt Creator in order to start
developing for your device. The following script does this for you.
\badcode
<INSTALL_DIR>/5.5/Boot2Qt/sources/b2qt-build-scripts/embedded-common/setup_qtcreator.sh
\endcode
This will set up a new kit in Qt Creator, using the toolchain and Qt from
your build directory. The new kit is visible under \b Tools > \b Options
> \b {Build & Run} > \b Kits.
*/
|
