Add platform-specific README's.

These files were previously added to source packages by the packaging
system.  There's no reason why these files shouldn't be available to
repo users too.

Reviewed-by: Trust Me

1 files changed, 44 insertions, 0 deletions

diff --git a/README.wince b/README.wince
new file mode 100644
index 0000000..27dfd60
--- /dev/null
+++ b/README.wince
@@ -0,0 +1,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
+}
+...
+