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
|
/****************************************************************************
**
** Copyright (C) 2010 Nokia Corporation and/or its subsidiary(-ies).
** All rights reserved.
** Contact: Nokia Corporation (qt-info@nokia.com)
**
** This file is part of the documentation of the Qt Toolkit.
**
** $QT_BEGIN_LICENSE:FDL$
** Commercial Usage
** Licensees holding valid Qt Commercial licenses may use this file in
** accordance with the Qt Commercial License Agreement provided with the
** Software or, alternatively, in accordance with the terms contained in a
** written agreement between you and Nokia.
**
** GNU Free Documentation License
** Alternatively, this file may be used under the terms of the GNU Free
** Documentation License version 1.3 as published by the Free Software
** Foundation and appearing in the file included in the packaging of this
** file.
**
** If you have questions regarding the use of this file, please contact
** Nokia at qt-info@nokia.com.
** $QT_END_LICENSE$
**
****************************************************************************/
/*!
\page qt-embedded-deployment.html
\title Deploying Qt for Embedded Linux Applications
\ingroup qt-embedded-linux
The procedure of deploying an Qt application on \l{Qt for Embedded Linux}
is essentially the same as the deployment procedure on X11 platforms
which is described in detail in the \l {Deploying an Application
on X11 Platforms} documentation. See also the \l {Deploying Qt
applications}{general remarks} about deploying Qt applications.
In addition, there is a couple of Qt for Embedded Linux specific issues to
keep in mind:
\tableofcontents
\section1 Fonts
When Qt for Embedded Linux applications run, they look for a file called
\c fontdir in Qt's \c /lib/fonts/ directory defining the
fonts that are available to the application (i.e. the fonts
located in the mentioned directory).
For that reason, the preferred fonts must be copied to the \c
/lib/fonts/ directory, and the \c fontdir file must be customized
accordingly. See the \l {Qt for Embedded Linux Fonts}{fonts} documentation
for more details about the supported font formats.
Note that the application will look for the \c /lib/fonts/
directory relative to the path set using the \c -prefix parameter
when running the \c configure script; ensure that this is a
sensible path in the target device environment. See the
\l {Installing Qt on Embedded Linux#Step 3: Building the
Library}{installation} documentation for more details.
\section1 Environment Variables
In general, any variable value that differs from the provided
default values must be set explicitly in the target device
environment. Typically, these include the QWS_MOUSE_PROTO,
QWS_KEYBOARD and QWS_DISPLAY variables specifying the drivers for
pointer handling, character input and display management,
respectively.
For example, without the proper mouse and keyboard drivers, there
is no way to give any input to the application when it is
installed on the target device. By running the \c configure script
using the \c -qt-kbd-<keyboarddriver> and \c
-qt-mouse-<mousedriver> options, the drivers are enabled, but in
addition the drivers and the preferred devices must be specified
as the ones to use in the target environment, by setting the
environment variables.
See the \l{Qt for Embedded Linux Pointer Handling}{pointer handling},
\l{Qt for Embedded Linux Character Input}{character input} and
\l{Qt for Embedded Linux Display Management}{display management}
documentation for more information.
\section1 Framebuffer Support
No particular actions are required to enable the framebuffer on
target devices: The Linux framebuffer is enabled by default on all
modern Linux distributions. For information on older versions, see
\l http://en.tldp.org/HOWTO/Framebuffer-HOWTO.html.
To test that the Linux framebuffer is set up correctly, and that
the device permissions are correct, use the program provided by
the \l {Testing the Linux Framebuffer} document.
*/
|
