-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Mahabhashyam Anupama
Sent: Thursday, 27 November 2003 2:47 PM
To: [EMAIL PROTECTED]
Subject: RE: Win CE 3.0 with OpenSSLThanks for the quick reply. I did run that bat file and also tried setting the path in environment variables from control panel settings. However, setting at command prompt seemed to do the trick. Well, its never easy for novices like me...now I have a new error:
clarm.exe /Fotmp32_ARM\dso_win32.obj -Iinc32 -Itmp32_ARM /W3 /WX /Ox /O2 /Ob2 /Gs0 /GF /Gy /nologo -D
WCEPLATFORM=MS_POCKET_PC_2000 -DARM -D_ARM_ -DUNDER_CE=300 -D_WIN32_CE=300 -DUNICODE -D_UNICODE -DWIN32 -DWIN3
2_LEAN_AND_MEAN -DL_ENDIAN -DDSO_WIN32 -DNO_CHMOD -IC:\openssl\wcecompat/include /Fdout32_ARM -DOPENSSL_NO_KRB
5 -c .\crypto\dso\dso_win32.c
dso_win32.c
.\crypto\dso\dso_win32.c(125) : error C2220: warning treated as error - no object file generated
.\crypto\dso\dso_win32.c(125) : warning C4133: 'function' : incompatible types - from 'char *' to 'const unsig
ned short *'
.\crypto\dso\dso_win32.c(210) : warning C4133: 'function' : incompatible types - from 'const char *' to 'const
unsigned short *'
.\crypto\dso\dso_win32.c(241) : warning C4133: 'function' : incompatible types - from 'const char *' to 'const
unsigned short *'
NMAKE : fatal error U1077: 'clarm.exe' : return code '0x2'
Stop.
Share holiday photos without swamping your Inbox. Get MSN Extra Storage now! ______________________________________________________________________ OpenSSL Project http://www.openssl.org User Support Mailing List [EMAIL PROTECTED] Automated List Manager [EMAIL PROTECTED]
Title: Message
The
code listed in the error below shouldn't be compiled for WINCE due to the #ifdef
at the top of that module. What has most likely happened is that
OPENSSL_SYS_WINCE is not being defined. I haven't tried building OpenSSL
on WINCE since 0.9.7 or 0.9.7a but it doesn't look like anything has changed in
this area. Have you performed the "perl Configure VC-CE"
step listed in INSTALL.WCE? This step result in OPENSSL_SYSNAME_WINCE
being defined which should result in OPENSSL_SYS_WINCE being defined when
e_os2.h is included indirectly by dso_win32.c.
As for
your previous problem, you might want to determine why INCLUDE wasn't set when
running WCEARM.BAT since it may signal a problem with your SDK
setup.
- Re: Win CE 3.0 with OpenSSL Mahabhashyam Anupama
- RE: Win CE 3.0 with OpenSSL Steven Reddie
- Re: Win CE 3.0 with OpenSSL Mahabhashyam Anupama
- RE: Win CE 3.0 with OpenSSL Steven Reddie
- RE: Win CE 3.0 with OpenSSL Mahabhashyam Anupama
- RE: Win CE 3.0 with OpenSSL Steven Reddie
- RE: Win CE 3.0 with OpenSSL Mahabhashyam Anupama
- RE: Win CE 3.0 with OpenSSL Steven Reddie
- RE: Win CE 3.0 with OpenSSL Mahabhashyam Anupama
- RE: Win CE 3.0 with OpenSSL Steven Reddie
- integrating OpenSSL into a cross platfor... tuviah snyder
- RE: Win CE 3.0 with OpenSSL Mahabhashyam Anupama
- re[2]: Win CE 3.0 with OpenSSL Jeff Roberts