|
1 /**************************************************************************** |
|
2 ** |
|
3 ** Copyright (C) 2010 Nokia Corporation and/or its subsidiary(-ies). |
|
4 ** All rights reserved. |
|
5 ** Contact: Nokia Corporation (qt-info@nokia.com) |
|
6 ** |
|
7 ** This file is part of the documentation of the Qt Toolkit. |
|
8 ** |
|
9 ** $QT_BEGIN_LICENSE:LGPL$ |
|
10 ** No Commercial Usage |
|
11 ** This file contains pre-release code and may not be distributed. |
|
12 ** You may use this file in accordance with the terms and conditions |
|
13 ** contained in the Technology Preview License Agreement accompanying |
|
14 ** this package. |
|
15 ** |
|
16 ** GNU Lesser General Public License Usage |
|
17 ** Alternatively, this file may be used under the terms of the GNU Lesser |
|
18 ** General Public License version 2.1 as published by the Free Software |
|
19 ** Foundation and appearing in the file LICENSE.LGPL included in the |
|
20 ** packaging of this file. Please review the following information to |
|
21 ** ensure the GNU Lesser General Public License version 2.1 requirements |
|
22 ** will be met: http://www.gnu.org/licenses/old-licenses/lgpl-2.1.html. |
|
23 ** |
|
24 ** In addition, as a special exception, Nokia gives you certain additional |
|
25 ** rights. These rights are described in the Nokia Qt LGPL Exception |
|
26 ** version 1.1, included in the file LGPL_EXCEPTION.txt in this package. |
|
27 ** |
|
28 ** If you have questions regarding the use of this file, please contact |
|
29 ** Nokia at qt-info@nokia.com. |
|
30 ** |
|
31 ** |
|
32 ** |
|
33 ** |
|
34 ** |
|
35 ** |
|
36 ** |
|
37 ** |
|
38 ** $QT_END_LICENSE$ |
|
39 ** |
|
40 ****************************************************************************/ |
|
41 |
|
42 /*! |
|
43 \page windowsce-signing.html |
|
44 \ingroup qtce |
|
45 \title Windows CE - Signing |
|
46 \brief How to sign Qt projects for use with Windows CE. |
|
47 |
|
48 \section1 Signing on Windows CE |
|
49 |
|
50 Windows CE provides a security mechanism to ask the user to confirm |
|
51 that they want to use an application/library that is unknown to the |
|
52 system. This process gets repeated for each dependency of an |
|
53 application, meaning each library the application links to, which is |
|
54 not recognized yet. |
|
55 |
|
56 To simplify this process you can use signatures and certificates. A |
|
57 certificate gets installed on the device and each file which is |
|
58 signed with the according certificate can be launched without the |
|
59 security warning. |
|
60 |
|
61 If you want to use signatures for your project written in Qt, |
|
62 configure provides the \c -signature option. You need to specify the |
|
63 location of the .pfx file and qmake adds the signing step to the |
|
64 build rules. |
|
65 |
|
66 If you need to select a separate signature for a specific project, |
|
67 or you only want to sign a single project, you can use the |
|
68 "SIGNATURE_FILE = foo.pfx" rule inside the project file. |
|
69 |
|
70 The above described rules apply for command line makefiles as well as |
|
71 Visual Studio projects generated by qmake. |
|
72 |
|
73 Microsoft usually ships development signatures inside the SDK packages. |
|
74 You can find them in the Tools subdirectory of the SDK root folder. |
|
75 |
|
76 Example: |
|
77 |
|
78 \list |
|
79 \o Calling configure with signing enabled: |
|
80 \code |
|
81 configure.exe -platform win32-msvc2005 -xplatform wincewm50pocket-msvc2005 -signature C:\some\path\SDKSamplePrivDeveloper.pfx |
|
82 \endcode |
|
83 |
|
84 \o Using pro file to specify signature |
|
85 \code |
|
86 ... |
|
87 TARGET = foo |
|
88 |
|
89 wince*: { |
|
90 SIGNATURE_FILE = somepath\customSignature.pfx |
|
91 } |
|
92 ... |
|
93 \endcode |
|
94 \endlist |
|
95 |
|
96 */ |