[Code and binaries can be downloaded from
http://www.it.uc3m.es/pervasive/wce_lite_compat/ ]
This patch makes some fixes to the last OpenSSL official version 0.9.8a.
First of all you have to realize that we're reluctant to accept
functional patches to released code. Meaning that if you want to see
your submission in official OpenSSL distribution, then you *have to*
target HEAD branch, not 0.9.8. When we see it working in HEAD, *then*
one can discuss back-port to released code base [if of actual interest
by that time].
Now as for submission itself. As far as I can tell it essentially boils
down to following things.
1. Tiny patches for missing _IONBF definition, #define ftime _ftime, int
_fmode declaration in apps/apps.c, #include <stdlib.h> in couple of
places... All in additional #ifdef WCE_ON_DEVICE_CONSOLE/#endif.
2. wce_lite_compat which implements open/read/write/close and stat.
3. Duplicate code in VC-32.pl to allow for extra WCE_ON_DEVICE_CONSOLE
and link PortSDK, generate separate makefile for the target.
Well, I still fail to see why either is necessary. "Still" refers to the
fact I've earlier commented on submission from you, guys, in similar
manner, i.e. "why do you want to treat your target so special?" Think in
more general terms!
As for 1. I'd rather #ifndef _IONBF affected code; implement own ftime
on all CE [or use some WIN32 API on all WIN32! say GetSystemTime]; get
rid of _fmode altogether; #include <stdlib.h> unconditionally...
As for 2. I'd rather eradicate all references to open/read/write/close
as well as stat for all Windows CE. It's perfectly possible!
As for 3. I'd rather check for an environment variable, say PORTSDK, and
emit makefile which would link with it without duplicating code or
separate makefile.
This way it would be possible to reduce build instructions to "setup
either WCECOMPAT or PORTSDK environment variable, but not both, and
compile." How does it sound? A.
______________________________________________________________________
OpenSSL Project http://www.openssl.org
Development Mailing List [email protected]
Automated List Manager [EMAIL PROTECTED]
