Please! Why is WCE support problematic? Because it's not actively
tested. What one can do? Converge it with platform that is tested more
regularly, "regular" Win32. Is it possible? I see no technical
obstacles. Except for problem of *another* character, namely testing of
the unified code on WCE. This is what we need help with, not more
suggestions for CE-specific code. So question is still if you can
confirm if you can compile previously mentioned e_capi.c as well as just
committed http://cvs.openssl.org/chngview?cn=23126?
As for VC-32.pl and /M* flags. As for `cl 2>&1`. In environments I've
checked it was the matter of which cl is on %PATH%, but it was always
cl. And version in script refers to ARM version, not X86. But there
surely is some reason for question. So what is it? Is your compiler
called something else? This is also something we desperately need help
with, taking consideration various environment factors. Yet, at the same
time we don't want to end up in situation that script works in very
specific configuration. So we need to be creative and keep it flexible.
So it's likely to be more of a dialog and iterations, than just
"path-that-works-for-me-end-of-discussion".
patch resubmitted WITH no attachment of zip file containing 2 useful
scripts to compile openssl on WCE and W32.
Anyway those 2 scripts are identical to those you can find on v100a for
WCE patch here : http://rt.openssl.org/index.html?q=2350
zips appear corrupted, I can't open them.
______________________________________________________________________
OpenSSL Project http://www.openssl.org
Development Mailing List openssl-dev@openssl.org
Automated List Manager majord...@openssl.org
