The approach I took with wcecompat and integration with OpenSSL was to make OpenSSL have as little special knowledge of CE as possible.
And my suggestion is to identify unnecessary code in given context and instead of striving for patching holes, just eliminate the redundant code. E.g. [at least] in CE context I figure one can drop Unix-ish open/read/write/close, which are used only in bss_fd.c, which in turn is not used anywhere in OpenSSL. And most stat calls are redundant and can be eliminated. This would elimitate need for suggested wce_lite_compat.
This means that wcecompat emulates missing ANSI/Posix functionality so that OpenSSL simply continues to program to the standard interfaces.
So does portsdk.
Wcecompat should be replaceable with very minor changes to OpenSSL, hopefully only where $WCECOMPAT is referenced in VC-32.pl.
They suggest to replace it with PortSDK *and* wce_lite_compat and my suggestion is to replace it with PortSDK *alone*. Well, "replace" is wrong term. "*Choose* between wcecompat and portsdk" is more appropraite.
The submitted patches referenced in the email below are much larger than I'd expect
Yes, the patch is total mess. It's *reverse* diff between configured trees. As mentioned essential chanages to source are tiny and I reckon that they can/should be generalized, most specifically I see no need to tag them with #ifdef THIS_IS_MY_VERY_SPECIAL_TARGET.
Not that there's anything special about my library, but what's the solution should a few more groups want their own CE compatibility layer included? Assuming they all do little more than provide the missing ANSI/Posix functionality then the only changes they should require to OpenSSL (above what have already been made) are to reference the new library in VC-32.pl and select it via config/Configure.
My suggestion is to select alternative library rather through environment variable, than through separate target lines in config. I think one VC-CE line is enough, at least for now. Cheers. A.
______________________________________________________________________ OpenSSL Project http://www.openssl.org Development Mailing List [email protected] Automated List Manager [EMAIL PROTECTED]
