Hi, > One of the concern I am involved with is also UNICODE AND ANSI versions > of stunnel...
I want to point out two things in the UNICODE vs. ANSI context. OpenSSL Win64 builds are actually compiled as UNICODE, and that it's possible to compile even Win32 build as UNICODE by passing -DUNICODE -D_UNICODE at configuration stage. > Well, that said, common code is just sometimes NOT possible, for fews > things : a lib named differently (ws2.lib for WCE, ws2_32.lib in > W32...comctl32.lib in W32, commctrl in WCE)... > or type missing, but simple to redefined... When I referred to "common code" I really referred to C code, not libraries. Even in this context I'm not saying that common code is *always* possible, only that it should be preferred/priority option. As for missing types, the problem is not really WCE (or even Windows) specific, and we take it on case to case basis, i.e. there is no common approach. > ... > ========= > Something else : look at VC-32.pl, my patch is correcting a typo ...: > in the original VC-32, line 125, there is written dbg_cLfags instead of > dbg_cFlags... > > So when will this be corrected ? The typo was corrected (1/2 hour after _ftime replacement). I've also just committed http://cvs.openssl.org/chngview?cn=23131. Please review. Note that I've chosen to skip version check and look at compiler name. As you report eVC has unique compiler names (and recognize /MC), while later Studio compilers are all called cl (and recognize same options as x86 compiler). It might appear ad-hoc, but it's not worse than version check. Whenever you confirm that it appears appropriate, it goes down to 1.0.2 branch. Same applies to _ftime and e_capi.c code (i.e. when you confirm that it works). Proceeding with further review... As for INSTALL.WCE and "openssl team want[ing] people to use full MS Visual Studio above or equal to 2005". As implied earlier, WCE is not regularly tested by any of OpenSSL team members and there is no expressed will. I mean it's not about what "team" wants, it's about unrelated contributors bringing pieces of information. As contributions are effectively unrelated, there is no guarantee that they don't contradict. On the contrary, they tend to be contradicting, and that actually why we are having this very discussion:-) Cheers. ______________________________________________________________________ OpenSSL Project http://www.openssl.org Development Mailing List openssl-dev@openssl.org Automated List Manager majord...@openssl.org
