Hi Frank, I've got a lot going on right now, meaning that I don't have time to look at this in detail. Generally speaking though, the goal of wcecompat was to fill the gap between what the Windows CE C Runtime Library offered and what a full ANSI/Posix Runtime Library should offer. Time constraints meant that the gap filled more closely matched the parts of ANSI/Posix that were needed by OpenSSL. I would hope that over time Microsoft would have filled these gaps themselves. It sounds like they've done some of this in eVC4.
My recollection is that Microsoft renamed some of the possible TARGETCPU values between eVC++ 3 and 4. ARM to ARMV4 was one of them. Wcecompat and the OpenSSL patches were written against eVC3 so expect the same naming convention. Modifying the WCEARMV4.BAT file included with eVC4 is the wrong approach; a hack! Instead wcecompat and OpenSSL need to be modified to work with both eVC3 and eVC4. This is what I did in my yet-to-be-completed patches which I'm not likely to find any time soon. The changes were trivial though and could easily be repeated. Regards, Steven -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Farkas Levente Sent: Tuesday, 28 June 2005 12:39 AM To: [email protected] Subject: Re: windows ce port patches hi Steven, sorry for the delay i was on vacation:-) of course i use you wcecompat lib at the first place, but i've to modify it a bit. first the makefiles to update to the current ce versions: http://www.lfarkas.org/pocket-pc/openssl/make.patch second have to remove a lots of 'fixes' from wcecompat which already fixed in eVC++ 4 sp4 so remove these include files (i'm not 100% check them, but it seems so): include/assert.h include/ctype.h include/malloc.h include/math.h include/memory.h include/setjmp.h include/stdarg.h include/stddef.h include/stdio.h include/stdlib.h include/string.h include/time.h but it would need a bit more time and more carefull examination to see what can be dropped (or fix) in the current wcecompat to update to the latest eVC++ 4 sp4. another patch which i create this one: http://www.lfarkas.org/pocket-pc/openssl/openssl-ce.patch which are mainly bugfix in the current openssl code and only win ce specific so it could be apply without hurt other part of the openssl code. another stange problem for after reading this mail: http://marc.theaimsgroup.com/?l=openssl-users&m=111712574012234&w=2 why have to change the TARGETCPU=ARM? since the eVC++ setup use the ARMV4 as the target cpu, but it's true that openssl can't build without it. and there are a few more problems... i look into this port problem again in this week and sen my new results. ps. another note that the current 0.9.8-beta6 is totaly broken and i fall back to the 0.9.7g after start with the new beta:-( yours. Steven Reddie wrote: > 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]
