Hi Levente,

I did the Windows CE port but have not found the time to complete an update
for the latest compiler and SDKs.  I think the last kit I used for the
current OpenSSL support was eVC 3.0 for PPC2002.

OPENSSL_SYS_WINCE is the correct tag to use; you'll find these in the source
code already.  I changed the makefiles and wcecompat extensively to support
more devices but I don't know when I'll get around to digging it up again.
As a minimal fix you shouldn't find that you need to change very much to get
things working with eVC 4.x.

Regards,

Steven

-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
On Behalf Of Farkas Levente
Sent: Tuesday, 14 June 2005 10:54 PM
To: [email protected]
Subject: windows ce port

hi,
it seems to me that no one realy cares about the windows ce port of openssl.
so i look around and try to fix the problems with the current stable release
0.9.7g and the current embedded visual c++. i'll send the required patch to
be able to compile on windows ce. but i wouldn't like to touch other
enviroments, so in some places i'd like to ifdef my modification. which
macro should i use for this (what is the prefered way):
- WCEPLATFORM
- UNDER_CE
- WIN32_CE
- OPENSSL_SYS_WINCE
thanks in advance.
yours.

ps. does this the right list for sending patches or should i use
openssl-users (since i saw previous post on that list)?

-- 
   Levente                               "Si vis pacem para bellum!"

______________________________________________________________________
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]

Reply via email to