]>
Commit | Line | Data |
---|---|---|
0bf23d9b RL |
1 | |
2 | INSTALLATION FOR THE WINDOWS CE PLATFORM | |
3 | ---------------------------------------- | |
4 | ||
5 | Building OpenSSL for Windows CE requires the following external tools: | |
6 | ||
7 | * Microsoft eMbedded Visual C++ 3.0 | |
8 | * wcecompat compatibility library (www.essemer.com.au) | |
9 | * Optionally ceutils for running automated tests (www.essemer.com.au) | |
10 | ||
293bb4b1 RL |
11 | You also need Perl for Win32. You will need ActiveState Perl, available |
12 | from http://www.activestate.com/ActivePerl. | |
13 | ||
a067cba3 RL |
14 | Windows CE support in OpenSSL relies on wcecompat. All Windows CE specific |
15 | issues should be directed to www.essemer.com.au. | |
16 | ||
0bf23d9b RL |
17 | The C Runtime Library implementation for Windows CE that is included with |
18 | Microsoft eMbedded Visual C++ 3.0 is incomplete and in some places | |
19 | incorrect. wcecompat plugs the holes and tries to bring the Windows CE | |
20 | CRT to a level that is more compatible with ANSI C. wcecompat goes further | |
21 | and provides low-level IO and stream IO support for stdin/stdout/stderr | |
22 | (which Windows CE does not provide). This IO functionality is not needed | |
23 | by the OpenSSL library itself but is used for the tests and openssl.exe. | |
24 | More information is available at www.essemer.com.au. | |
25 | ||
26 | Building | |
27 | -------- | |
28 | ||
0bf23d9b RL |
29 | Setup the eMbedded Visual C++ environment. There are batch files for doing |
30 | this installed with eVC++. For an ARM processor, for example, execute: | |
31 | ||
32 | > "C:\Program Files\Microsoft eMbedded Tools\EVC\WCE300\BIN\WCEARM.BAT" | |
33 | ||
34 | Next indicate where wcecompat is located: | |
35 | ||
36 | > set WCECOMPAT=C:\wcecompat | |
37 | ||
38 | Next you should run Configure: | |
39 | ||
40 | > perl Configure VC-CE | |
41 | ||
42 | Next you need to build the Makefiles: | |
43 | ||
44 | > ms\do_ms | |
45 | ||
46 | If you get errors about things not having numbers assigned then check the | |
47 | troubleshooting section in INSTALL.W32: you probably won't be able to compile | |
48 | it as it stands. | |
49 | ||
50 | Then from the VC++ environment at a prompt do: | |
51 | ||
52 | - to build static libraries: | |
53 | ||
54 | > nmake -f ms\ce.mak | |
55 | ||
56 | - or to build DLLs: | |
57 | ||
58 | > nmake -f ms\cedll.mak | |
59 | ||
60 | If all is well it should compile and you will have some static libraries and | |
61 | executables in out32, or some DLLs and executables in out32dll. If you want | |
62 | to try the tests then make sure the ceutils are in the path and do: | |
63 | ||
64 | > cd out32 | |
65 | > ..\ms\testce | |
66 | ||
f503c2c9 RL |
67 | This will copy each of the test programs to the Windows CE device and execute |
68 | them, displaying the output of the tests on this computer. The output should | |
69 | look similar to the output produced by running the tests for a regular Windows | |
70 | build. | |
71 |