projects / thirdparty / openssl.git / blame
| 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 | ||
| b87e2576 RL |
11 | You also need Perl for Win32. You will need ActiveState Perl, available |
| 12 | from http://www.activestate.com/ActivePerl. | |
| 13 | ||
| 0bf23d9b RL |
14 | The C Runtime Library implementation for Windows CE that is included with |
| 15 | Microsoft eMbedded Visual C++ 3.0 is incomplete and in some places | |
| 16 | incorrect. wcecompat plugs the holes and tries to bring the Windows CE | |
| 17 | CRT to a level that is more compatible with ANSI C. wcecompat goes further | |
| 18 | and provides low-level IO and stream IO support for stdin/stdout/stderr | |
| 19 | (which Windows CE does not provide). This IO functionality is not needed | |
| 20 | by the OpenSSL library itself but is used for the tests and openssl.exe. | |
| 21 | More information is available at www.essemer.com.au. | |
| 22 | ||
| 23 | Building | |
| 24 | -------- | |
| 25 | ||
| 0bf23d9b RL |
26 | Setup the eMbedded Visual C++ environment. There are batch files for doing |
| 27 | this installed with eVC++. For an ARM processor, for example, execute: | |
| 28 | ||
| 29 | > "C:\Program Files\Microsoft eMbedded Tools\EVC\WCE300\BIN\WCEARM.BAT" | |
| 30 | ||
| 31 | Next indicate where wcecompat is located: | |
| 32 | ||
| 33 | > set WCECOMPAT=C:\wcecompat | |
| 34 | ||
| 35 | Next you should run Configure: | |
| 36 | ||
| 37 | > perl Configure VC-CE | |
| 38 | ||
| 39 | Next you need to build the Makefiles: | |
| 40 | ||
| 41 | > ms\do_ms | |
| 42 | ||
| 43 | If you get errors about things not having numbers assigned then check the | |
| 44 | troubleshooting section in INSTALL.W32: you probably won't be able to compile | |
| 45 | it as it stands. | |
| 46 | ||
| 47 | Then from the VC++ environment at a prompt do: | |
| 48 | ||
| 49 | - to build static libraries: | |
| 50 | ||
| 51 | > nmake -f ms\ce.mak | |
| 52 | ||
| 53 | - or to build DLLs: | |
| 54 | ||
| 55 | > nmake -f ms\cedll.mak | |
| 56 | ||
| 57 | If all is well it should compile and you will have some static libraries and | |
| 58 | executables in out32, or some DLLs and executables in out32dll. If you want | |
| 59 | to try the tests then make sure the ceutils are in the path and do: | |
| 60 | ||
| 61 | > cd out32 | |
| 62 | > ..\ms\testce | |
| 63 |