In message [EMAIL PROTECTED] on Mon, 18 Nov 2002
22:24:18 +1100, Steven Reddie [EMAIL PROTECTED] said:
smr Since I'm using the MSVC++ /W3 /WX options (max warnings, treat warnings as
smr errors), the following two numbered lines in x509_vfy.c are giving errors:
smr time_t offset;
smr
In message [EMAIL PROTECTED] on Mon, 18 Nov 2002
00:51:36 +1100, Steven Reddie [EMAIL PROTECTED] said:
smr This will copy each of the test programs to the Windows CE device and
smr execute
smr them, displaying the output of the tests on this computer. The output
smr should
smr look similar
In message [EMAIL PROTECTED] on Sat, 16 Nov 2002
14:50:33 +1100, Steven Reddie [EMAIL PROTECTED] said:
smr I thought that OPENSSL_SYSNAME_* was the new way of doing things, so I
smr changed the Microsoft standard UNDER_CE to OPENSSL_SYSNAME_WINCE at the last
smr minute. I think I had to pull in
In message [EMAIL PROTECTED] on Sat, 16 Nov 2002
15:15:10 +1100, Steven Reddie [EMAIL PROTECTED] said:
smr Could you please replace util/pl/VC-CE.pl with the one in the
smr root directory, or just change the double quotes around $lflags
smr at line#16 with single quotes.
Done and committed.
--
In message [EMAIL PROTECTED] on Sat, 16 Nov 2002
15:18:12 +1100, Steven Reddie [EMAIL PROTECTED] said:
smr Everything is done from the Windows box. The test*ce*.bat files use cecopy
smr to copy files to the device and cerun to invoke the test programs. The
smr output of the tests is redirected
Thanks! Looks good for the most part, the only thing that's just
non-traditional is the direct use of OPENSSL_SYSNAME_WINCE, but
that's easily taken care of.
Oh, yeah, is there any reason to keep VC-CE.pl (as opposed to
util/pl/VC-CE.pl)?
--
Richard Levitte \ Spannvägen 38, II \ [EMAIL
OK, there are a couple of things that are unclear to me:
1. INSTALL.WCE is a very good description, although it should have
Perl among the list of requirements at the beginning. I can add
that. One thing is unclear, however: does one do everything on the
WinCE device? Or everything on
