OpenSSL's compilation under wince

1. The following external tools are required to compile OpenSSL under WinCE* Microsoft eMbedded Visual C + + 3.0 * Wcecompat Compatibility Library (www.essemer.com.au) * Optionally ceutils for run Ning Automated Tests (www.essemer.com.au) also requires Win32 Perl, such as ActiveState Perl (Http://www.activestate.com/ActivePerl) WinCE rely on Wcecompat to support OpenSSL, and if there are any problems, check http://www.essemer.com.au/windowsce/update. The current version of Wcecompat is 1.1, supporting WCE 4.2 and newer platforms, 2. The compilation process is as follows:1. Install emebedded Visual C + + development environment with batch files installed with evc++, for ARMV4 processors, execute: > C:/Program files/microsoft eMbedded C + + 4.0/evc/wce420 /bin/wcearmv4. BAT next Specifies the location of the Wcecompat folder (which may have an error in the following procedure in place outside the C-packing directory): > Set Wcecompat=c:/wcecompat then enter the OpenSSL installation package directory, for example: c:/ openssl-0.9.8a, execute Configure: > Perl Configure vc-ce then build makefile: > Ms/do_ms Create a static link library below: > Nmake-f Ms/ce.mak or Build DLL: > Nmake-f Ms/cedll.mak
If NMAKE prompts for a missing header or LIB file, there are two reasons why the Wcecompat has not yet been compiled to create Lib supplied to NMAKE, and the second is that the environment variable set by evc++ is incorrect. The former, entering the Wcecompat directory to perform nmake-f makefile, after succeeding, under the subdirectory Lib folder, There are wcecompat.lib and wcecompatex.lib two files; the latter, modify the Wcearmv4.bat files that were executed before, and add the Sdkroot directory to the installation directory of the SDK, respectively, after set include=;%sdkroot%/ %osversion%/%platform%/include/emulator and set lib= after adding;%sdkroot%/%osversion%/%platform%/lib/emulator; save changes and then nmake again The result of compiling OpenSSL is saved in the. In/openssl-0.9.8a/out32_armv4, there are two Lib or DLLs required and some test executable programs. Lib can be used under visual studio2005. 3. How to use OpenSSL-compiled results (Lib only): 1)         new visual studio2005 Smart Device Project 2)          Project-> Property->c/c++-> Additional Include directory, add wcecompat/include,openssl-0.9.8a/include two directories (according to individual set up full path) 3)          Project-> Properties-> linker-> Enter-> Additional dependencies, add Ssleay32.lib,libeay32.lib,wcecompat.lib, Wcecompatex.lib (if still not recognized, copy the four Lib files to the current project directory) 4         compile your own project if it appears: A.obj: Error lnk2019:unresolved external symbol __security_cookie referenced in function "void __cdecl mymethod (char *)" (? Mymet hod@ @YAXPEAD @z) a.obj:error lnk2019:unresolved external symbol __security_check_cookie referenced in function "void __c Decl MyMethod (char *) "(? mymethod@ @YAXPEAD @z) a.exe:fatal error lnk1120:2 unresolved issues, Project Externals properties-> > code generates-> buffer security check, "yes" to "No (/gs-)"