We have built Steven's "patch" successfully for PocketPC and PocketPC 2002. The issue is the many different hardware versions it needs to be compiled for. With the makefile approach (Steven's), a separate build has to be done for each CPU type - a somewhat labour-intensive exercise :-) Martin Erdrich's patch included an MS project file that let one build all N versions at one time. Any suggestions on how this can be handled in OpenSSL? If one is only building a specific CPU, the makefile is fine, but most developers/vendors will build for a larger set of CPU's. Chris Brook
-----Original Message----- From: [EMAIL PROTECTED] [mailto:owner-openssl-dev@;openssl.org]On Behalf Of Richard Levitte - VMS Whacker Sent: Friday, November 15, 2002 2:41 PM To: [EMAIL PROTECTED]; [EMAIL PROTECTED] Subject: Re: [PATCH] Windows CE support for 0.9.7 (against 20021114 snapshot) Thanks! Looks good for the most part, the only thing that's just "non-traditional" is the direct use of OPENSSL_SYSNAME_WINCE, but that's easily taken care of. Oh, yeah, is there any reason to keep VC-CE.pl (as opposed to util/pl/VC-CE.pl)? -- Richard Levitte \ Spannvägen 38, II \ [EMAIL PROTECTED] Redakteur@Stacken \ S-168 35 BROMMA \ T: +46-8-26 52 47 \ SWEDEN \ or +46-708-26 53 44 Procurator Odiosus Ex Infernis -- [EMAIL PROTECTED] Member of the OpenSSL development team: http://www.openssl.org/ Unsolicited commercial email is subject to an archival fee of $400. See <http://www.stacken.kth.se/~levitte/mail/> for more info. ______________________________________________________________________ OpenSSL Project http://www.openssl.org Development Mailing List [EMAIL PROTECTED] Automated List Manager [EMAIL PROTECTED] ______________________________________________________________________ OpenSSL Project http://www.openssl.org Development Mailing List [EMAIL PROTECTED] Automated List Manager [EMAIL PROTECTED]
