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
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
|
/****************************************************************************
**
** Copyright (C) 2012 Digia Plc and/or its subsidiary(-ies).
** Contact: http://www.qt-project.org/legal
**
** This file is part of the documentation of the Qt Toolkit.
**
** $QT_BEGIN_LICENSE:LGPL$
** Commercial License Usage
** Licensees holding valid commercial Qt licenses may use this file in
** accordance with the commercial license agreement provided with the
** Software or, alternatively, in accordance with the terms contained in
** a written agreement between you and Digia. For licensing terms and
** conditions see http://qt.digia.com/licensing. For further information
** use the contact form at http://qt.digia.com/contact-us.
**
** GNU Lesser General Public License Usage
** Alternatively, this file may be used under the terms of the GNU Lesser
** General Public License version 2.1 as published by the Free Software
** Foundation and appearing in the file LICENSE.LGPL included in the
** packaging of this file. Please review the following information to
** ensure the GNU Lesser General Public License version 2.1 requirements
** will be met: http://www.gnu.org/licenses/old-licenses/lgpl-2.1.html.
**
** In addition, as a special exception, Digia gives you certain additional
** rights. These rights are described in the Digia Qt LGPL Exception
** version 1.1, included in the file LGPL_EXCEPTION.txt in this package.
**
** GNU General Public License Usage
** Alternatively, this file may be used under the terms of the GNU
** General Public License version 3.0 as published by the Free Software
** Foundation and appearing in the file LICENSE.GPL included in the
** packaging of this file. Please review the following information to
** ensure the GNU General Public License version 3.0 requirements will be
** met: http://www.gnu.org/copyleft/gpl.html.
**
**
** $QT_END_LICENSE$
**
****************************************************************************/
/*!
\page windowsce-customization.html
\ingroup qtce
\title Windows CE - Working with Custom SDKs
\brief How to set up Qt for use with custom Windows CE SDKs.
When working with a custom SDK for Windows CE, Qt provides an easy way
to add support for it to your development environment. The following is
a tutorial that covers how to create a specification for Qt on Windows
CE platforms.
\tableofcontents
\section1 Creating a Custom Build Specification
Create a subdirectory in the \c mkspecs folder of the Qt directory.
New specifications for Qt for Windows CE following this naming convention:
\snippet doc/src/snippets/code/doc_src_wince-customization.qdoc 0
Using this convention makes it possible for \l{qmake} to identify that
you are building Qt for Windows CE, and will customize the compilation
process accordingly.
Create the files \c qmake.conf and \c qplatformdefs.h inside the new
specification directory. Take a look at the implementation of the other
Windows CE specifications included in the \c mkspecs directory to see
what is required to build Qt for Windows CE successfully.
\section1 Fine-Tuning Options
Compared to the desktop versions, Qt for Windows CE needs two additional
options:
\list
\o \bold{CE_SDK} specifies the name of the SDK.
\o \bold{CE_ARCH} specifies information about the target architecture.
\endlist
Following is an example configuration for the Windows Mobile 5 for
Pocket PC SDK:
\snippet doc/src/snippets/code/doc_src_wince-customization.qdoc 1
\note \l{qmake} uses this information to build a valid Visual Studio
project file. You need to ensure that they are identical to the
configuration of the custom SDK, otherwise you might not be able to compile
or debug your project with Visual Studio.
Additionally, most Windows CE SDKs use extra compiler options. These
can be specified by expanding the \c DEFINES value.
For example, with Windows Mobile 5 for Pocket PC, the \c DEFINES variable
is expanded in the following way:
\snippet doc/src/snippets/code/doc_src_wince-customization.qdoc 2
The mkspec may require additional configuration to be used inside of Visual
Studio, depending on the Windows CE SDK. The above example defines
\c _M_ARM. This definition is available internally in Visual Studio. Hence,
the compiler will warn you about redefinition during the build step. These
warnings can be disabled by adding a \c default_post.prf file containing
the following lines, within the subdirectory.
\snippet doc/src/snippets/code/doc_src_wince-customization.qdoc 8
\section1 Cross-compilation Environment for a Custom SDK
Qt for Windows CE supports a convenience script, \c{setcepaths.bat}, that
prepares the environment in a command prompt for cross-compilation.
However, on custom SDKs, the \c checksdk tool is provided to identify the
environment, so Qt compiles successfully.
\c checksdk is generated during the \c configure step and allows for the
following options:
\list
\o \c list: Returns a list of available Windows CE SDKs. (This list
may contain one or more SDKs not supported on Qt for Windows CE,
e.g., Pocket PC 2003.)
\o \c sdk: The parameter to specify an SDK. Returns a setup of
environment variables that must be set to cross-compile Qt.
\o \c script: Stores your setup in a \c{.bat} file. This simplifies
the process of switching environments when you load a command
prompt in future.
\endlist
\section1 Compiling Qt for a Custom SDK
Windows CE is highly customizable, hence it is possible that some SDKs have
feature-stripped setups. Depending on the SDK's configuration, Qt may not
compile in its standard configuration, as Qt for Windows CE is designed to
be compatible with the Standard SDK setup.
However, it is possible to exclude features of Qt and create a version that
compiles for the desired SDK.
Further information on stripping features can be found in the
\l{Fine-Tuning Features in Qt}{QFeatures} documentation.
\section1 Making Qt Applications Start on a Custom Device
Sometimes, a Windows CE device has been created with a configuration
different from the corresponding SDK's configuration. In this case, symbols
that were available at linking stage will be missing from the run-time
libraries.
Unfortunately, the operating system will not provide an error message that
mentions which symbols are absent. Instead, a message box with the following
message will appear:
\c{app.exe is not a valid CE application!}
To identify the missing symbols, you need to create a temporary
application that attempts to dynamically load the Qt for Windows CE
libraries using \c LoadLibrary. The following code can be used for this:
\snippet doc/src/snippets/code/doc_src_wince-customization.qdoc 9
Once you have compiled and deployed the application as well as the Qt
libraries, start a remote debugger. The debugger will then print the
ordinal number of the unresolved symbol.
Search for parts of Qt that rely on these functions and disable them using
the \l{Fine-Tuning Features in Qt}{QFeatures} functionality.
In our experience, when Qt applications do not start on Windows CE, it is
usually the result of missing symbols for the following classes or
features:
\list
\o \l{Drag and Drop}
\o \l{QClipboard}
\o \l{QCursor}
\endlist
Please refer to the Microsoft documentation
\l{http://msdn.microsoft.com/en-us/library/e7tsx612.aspx}{here} for
information on what ordinals are and how you can create them. Information
on accessing the corresponding symbol name to a given ordinal value can
also be found in the Microsoft documentation.
*/
/*!
\page shadow builds-wince.html
\ingroup qtce
\title Windows CE - Using shadow builds
\brief How to create a shadow build for Qt for Windows CE.
\tableofcontents
While developing for Windows CE you might want to compile a
version of Qt for several different platforms and SDKs. In order
to create those different builds of Qt you do not have to copy the
whole Qt package or the Qt source. You are able to create multiple
Qt builds from a single source tree. Such builds are called shadow
builds.
Basically a shadow build is created by calling configure.exe from a
different directory.
To make sure that the shadow build compiles correctly it is important
that you following these guidelines:
\list
\o The original Qt source package must be left untouched - configure must
never have been run in the source tree directory.
\o The shadow build directory must be on the same level as the Qt source
package.\br
If the Qt package is in \c{C:\Qt\%VERSION%} the shadow build directory
could be \c{C:\Qt\shadowbuild}. A shadow build from a directory like
\c{C:\shadowbuild} will not compile.
\o Avoid using "release" and "debug" in the path to the shadow build
directory. (This is an internal limitation of the build system.)
\o The \c{\bin} directory of the shadow build directory must be added to the
\c PATH environment variable.
\o Perl has been installed on your system. (\l{ActivePerl} is a popular
distribution of Perl on Windows.)
\endlist
So lets assume you have installed Qt in \c{C:\Qt\%VERSION%} and you want
to create a shadow build in \c{C:\Qt\mobile5-shadow}:
\list
\o First add \c{C:\Qt\mobile5-shadow\bin} to the \c PATH variable.
\snippet doc/src/snippets/code/doc_src_wince-customization.qdoc 3
\o Make sure the enviroment variables for your compiler are set.
Visual Studio includes \c{vcvars32.bat} for that purpose - or simply use
the "Visual Studio Command Prompt" from the Start menu.
\o Now navigate to your shadow build directory and run configure:
\snippet doc/src/snippets/code/doc_src_wince-customization.qdoc 4
\o To build Qt, you have to update your \c{PATH, INCLUDE} and \c LIB paths
to point to your target platforms.
For a default installation of the Windows Mobile 5.0 Pocket PC SDK, you
can do the following:
\snippet doc/src/snippets/code/doc_src_wince-customization.qdoc 5
We have provided a convenience script for this called \c{setcepaths}. Simply
type:
\snippet doc/src/snippets/code/doc_src_wince-customization.qdoc 6
\o Finally, to build the shadow build type:
\snippet doc/src/snippets/code/doc_src_wince-customization.qdoc 7
\o That's all. You have successfully created a shadow build of Qt in
\c{C:\Qt\mobile5-shadow}.
\endlist
*/
|
