blob: 27dfd603544ef866a0242931a01db2e2d92fa806 (
plain)
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
|
Signing on Windows CE.
Windows CE provides a security mechanism to ask the user to confirm
that he wants to use an application/library, which is unknown to the
system. This process gets repeated for each dependency of an
application, meaning each library the application links to, which is
not recognized yet.
To simplify this process you can use signatures and certificates. A
certificate gets installed on the device and each file which is
signed with the according certificate can be launched without the
security warning.
In case you want to use signatures for your project written in Qt,
configure provides the -signature option. You need to specify the
location of the .pfx file and qmake adds the signing step to the
build rules.
If you need to select a separate signature for a specific project,
or you only want to sign this single project, you can use the
"SIGNATURE_FILE = foo.pfx" rule inside the project file.
The above decribed rules apply for command line makefiles as well as
Visual Studio projects generated by qmake.
Microsoft usually ships development signatures inside the SDK packages.
You can find them in the Tools subdirectory of the SDK root folder.
Example:
1. calling configure with signing enabled:
configure.exe -platform win32-msvc2005 -xplatform wincewm50pocket-msvc2005
-signature C:\some\path\SDKSamplePrivDeveloper.pfx
2. using pro file to specify signature
[inside .pro file]
...
TARGET = foo
wince*: {
SIGNATURE_FILE = somepath\customSignature.pfx
}
...
|
