Re: OPENSSL for windows mobile 5/6

74 views
Skip to first unread message

RaviVyas

unread,
May 22, 2014, 9:24:45 AM5/22/14
to
hello sir,
i have compiled wcecompat for my windows ce 6 app using TARGETCPU=x86 and
trying to build openSSL for that i am using openssl-0.9.8i version but i can
not built it perfectly and got lots of errors like this..

D:\my\ssl\openssl-OpenSSL_0_9_8-stable-1bcb94a>set INCLUDE=C:\Program Files
(x86
)\Microsoft Visual Studio 9.0\VC\ce\include;C:\Program Files (x86)\Microsoft
Vis
ual Studio9.0\VC\ce\atlmfc\include;C:\Program Files (x86)\Microsoft Visual
Studi
o 9.0\SmartDevices\SDK\SQL Server\Client\v2.0;C:\Program Files
(x86)\Microsoft V
isual Studio 9.0\SmartDevices\SDK\Smartphone2003\Include

D:\my\ssl\openssl-OpenSSL_0_9_8-stable-1bcb94a>set
LIB=C:\Users\kits\Desktop\WCE
601\Lib\x86\retail;C:\Program Files (x86)\Microsoft Visual Studio
9.0\VC\ce\atlm
fc\lib\x86;C:\ProgramFiles (x86)\Microsoft Visual Studio
9.0\VC\ce\lib\x86;C:\Pr
ogram Files\Microsoft SDKs\Windows\v6.0A\Lib\x64

D:\my\ssl\openssl-OpenSSL_0_9_8-stable-1bcb94a>set PATH=C:\Program
Files(x86)\Mi
crosoft Visual Studio 9.0\VC\ce\bin\x86_cex86;C:\Program Files
(x86)\Microsoft V
isual Studio 9.0\VC\bin;C:\Program Files (x86)\Microsoft Visual Studio
9.0\Commo
n7\Tools;C:\Program Files (x86)\Microsoft Visual Studio
9.0\Common7\IDE;C:\Progr
am Files (x86)\Microsoft Visual Studio 9.0\SDK\v3.5\Bin;C:\Program Files
(x86)\M
icrosoft Visual Studio 9.0;$(FrameworkSDKDir)Bin;%PATH%

D:\my\ssl\openssl-OpenSSL_0_9_8-stable-1bcb94a>set
WCECOMPAT=D:\my\ssl\wcecompat
-master

D:\my\ssl\openssl-OpenSSL_0_9_8-stable-1bcb94a>perl Configure VC-CE
Configuring for VC-CE
no-camellia [default] OPENSSL_NO_CAMELLIA (skip dir)
no-capieng [default] OPENSSL_NO_CAPIENG (skip dir)
no-cms [default] OPENSSL_NO_CMS (skip dir)
no-gmp [default] OPENSSL_NO_GMP (skip dir)
no-jpake [experimental] OPENSSL_NO_JPAKE (skip dir)
no-krb5 [krb5-flavor not specified] OPENSSL_NO_KRB5
no-mdc2 [default] OPENSSL_NO_MDC2 (skip dir)
no-montasm [default]
no-rc5 [default] OPENSSL_NO_RC5 (skip dir)
no-rfc3779 [default] OPENSSL_NO_RFC3779 (skip dir)
no-seed [default] OPENSSL_NO_SEED (skip dir)
no-shared [default]
no-zlib [default]
no-zlib-dynamic [default]
IsMK1MF=1
CC =cl
CFLAG =-DOPENSSL_THREADS -DDSO_WIN32
EX_LIBS =
CPUID_OBJ =
BN_ASM =bn_asm.o
DES_ENC =des_enc.o fcrypt_b.o
AES_ASM_OBJ =aes_core.o aes_cbc.o
BF_ENC =bf_enc.o
CAST_ENC =c_enc.o
RC4_ENC =rc4_enc.o rc4_skey.o
RC5_ENC =rc5_enc.o
MD5_OBJ_ASM =
SHA1_OBJ_ASM =
RMD160_OBJ_ASM=
PROCESSOR =
RANLIB =true
ARFLAGS =
PERL =perl
THIRTY_TWO_BIT mode
BN_LLONG mode
RC4_INDEX mode
RC4_CHUNK is undefined

Configured for VC-CE.

D:\my\ssl\openssl-OpenSSL_0_9_8-stable-1bcb94a>ms\do_ms

D:\my\ssl\openssl-OpenSSL_0_9_8-stable-1bcb94a>perl util\mkfiles.pl 1>MINFO

D:\my\ssl\openssl-OpenSSL_0_9_8-stable-1bcb94a>perl util\mk1mf.pl no-asm
VC-WIN3
2 1>ms\nt.mak

D:\my\ssl\openssl-OpenSSL_0_9_8-stable-1bcb94a>perl util\mk1mf.pl dll no-asm
VC-
WIN32 1>ms\ntdll.mak

D:\my\ssl\openssl-OpenSSL_0_9_8-stable-1bcb94a>if xWCE600 == x goto skipce

D:\my\ssl\openssl-OpenSSL_0_9_8-stable-1bcb94a>perl util\mk1mf.pl no-asm
VC-CE
1>ms\ce.mak

D:\my\ssl\openssl-OpenSSL_0_9_8-stable-1bcb94a>perl util\mk1mf.pl dll no-asm
VC-
CE 1>ms\cedll.mak

D:\my\ssl\openssl-OpenSSL_0_9_8-stable-1bcb94a>perl util\mkdef.pl 32 libeay
1>m
s\libeay32.def

D:\my\ssl\openssl-OpenSSL_0_9_8-stable-1bcb94a>perl util\mkdef.pl 32 ssleay
1>m
s\ssleay32.def

D:\my\ssl\openssl-OpenSSL_0_9_8-stable-1bcb94a>nmake -f ms\cedll.mak

Microsoft (R) Program Maintenance Utility Version 9.00.21022.08
Copyright (C) Microsoft Corporation. All rights reserved.

Building OpenSSL
perl util/copy.pl ".\crypto\buildinf.h" "tmp32dll_x86\buildinf.h"
Copying: ./crypto/buildinf.h to tmp32dll_x86/buildinf.h
perl util/copy.pl ".\crypto\opensslconf.h"
"inc32\openssl\opensslconf.h"

Copying: ./crypto/opensslconf.h to inc32/openssl/opensslconf.h
cl /Fotmp32dll_x86\cryptlib.obj -Iinc32 -Itmp32dll_x86 /MC /O1i /W3
/WX
/GF /Gy /nologo -DUNICODE -D_UNICODE -DOPENSSL_SYSNAME_WINCE
-DWIN32_LEAN_AND_M
EAN -DL_ENDIAN -DDSO_WIN32 -DNO_CHMOD -ID:\my\ssl\wcecompat-master/include
-DOPE
NSSL_SMALL_FOOTPRINT -D_WIN32_WCE=600 -DUNDER_CE=600 -DWCE_PLATFORM_VC-CE
-Dx86
-D_ /Fdout32dll_x86 -DOPENSSL_NO_CAMELLIA -DOPENSSL_NO_SEED -DOPENSSL_NO_RC5
-DO
PENSSL_NO_MDC2 -DOPENSSL_NO_CMS -DOPENSSL_NO_JPAKE -DOPENSSL_NO_CAPIENG
-DOPENSS
L_NO_KRB5 -DOPENSSL_NO_DYNAMIC_ENGINE -D_WINDLL -D_DLL
-DOPENSSL_BUILD_SHLIBCRY
PTO -c .\crypto\cryptlib.c
cl : Command line warning D9002 : ignoring unknown option '/MC'
cryptlib.c
C:\Program Files (x86)\Microsoft Visual Studio
9.0\SmartDevices\SDK\Smartphone20
03\Include\winnt.h(3019) : error C2061: syntax error : identifier 'PCONTEXT'
C:\Program Files (x86)\Microsoft Visual Studio
9.0\SmartDevices\SDK\Smartphone20
03\Include\winnt.h(3020) : error C2059: syntax error : '}'
C:\Program Files (x86)\Microsoft Visual Studio
9.0\SmartDevices\SDK\Smartphone20
03\Include\winbase.h(1481) : error C2061: syntax error : identifier
'LPCONTEXT'
C:\Program Files (x86)\Microsoft Visual Studio
9.0\SmartDevices\SDK\Smartphone20
03\Include\winbase.h(1481) : error C2059: syntax error : ';'
C:\Program Files (x86)\Microsoft Visual Studio
9.0\SmartDevices\SDK\Smartphone20
03\Include\winbase.h(2222) : error C2146: syntax error : missing ')' before
iden
tifier 'lpContext'
C:\Program Files (x86)\Microsoft Visual Studio
9.0\SmartDevices\SDK\Smartphone20
03\Include\winbase.h(2222) : error C2081: 'LPCONTEXT' : name in formal
parameter
list illegal
C:\Program Files (x86)\Microsoft Visual Studio
9.0\SmartDevices\SDK\Smartphone20
03\Include\winbase.h(2222) : error C2061: syntax error : identifier
'lpContext'
C:\Program Files (x86)\Microsoft Visual Studio
9.0\SmartDevices\SDK\Smartphone20
03\Include\winbase.h(2222) : error C2059: syntax error : ';'
C:\Program Files (x86)\Microsoft Visual Studio
9.0\SmartDevices\SDK\Smartphone20
03\Include\winbase.h(2223) : error C2059: syntax error : ')'
C:\Program Files (x86)\Microsoft Visual Studio
9.0\SmartDevices\SDK\Smartphone20
03\Include\winbase.h(2230) : error C2143: syntax error : missing ')' before
'*'
C:\Program Files (x86)\Microsoft Visual Studio
9.0\SmartDevices\SDK\Smartphone20
03\Include\winbase.h(2230) : error C2143: syntax error : missing '{' before
'*'
C:\Program Files (x86)\Microsoft Visual Studio
9.0\SmartDevices\SDK\Smartphone20
03\Include\winbase.h(2231) : error C2059: syntax error : ')'
NMAKE : fatal error U1077: '"C:\Program Files (x86)\Microsoft Visual Studio
9.0\
VC\bin\cl.EXE"' : return code '0x2'
Stop.



now second thing is that i can not compile my wcecompat for ARMV4I..!
so please help me out from this problem.
i am stuck in this problem from several days..!





--
View this message in context: http://openssl.6102.n7.nabble.com/OPENSSL-for-windows-mobile-5-6-tp38606p50243.html
Sent from the OpenSSL - Dev mailing list archive at Nabble.com.
______________________________________________________________________
OpenSSL Project http://www.openssl.org
Development Mailing List opens...@openssl.org
Automated List Manager majo...@openssl.org

Pierre DELAAGE

unread,
May 22, 2014, 11:59:06 AM5/22/14
to
Ok Ravi,
You asked me some help in private,
that I will reproduce here so that people can follow the complete thread :

"
Le 22/05/2014 15:39, Pierre DELAAGE a �crit :
> Hello,
> I am working on it myself,
> and particularly for my stunnel port.
> I will let you know.
>
> In the meantime : if you have downloaded my openssl V100a package for
WCE,
> open a command line window to the root folder of openssl package and then
>
> 1/ CUSTOMIZE the script "mywcebuild.bat" : it is self explanatory, 4
lines to check at the beginning
>
> 2/ when done : run this command line :
>
> mywcebuild ARMV4.
>
> 3/ then go to openssl folder/out32dll_ARMV4
>
> and take ssleay32.dll and libeay32.dll,
> and move them to your emulator...
>
> 4/ then YOU have to create an application using those dll...
> for your linker steps, you will need, from that same out32dll_ARMV4
folder :
>
> ssleay32.liband libeay32.lib
>
> and of course all the include files that are provided by openssl...
>
> NOTA : I reviewed your previous logs of compilation failure :
> this is because you are using the compiler from VSTUDIO 2005 and NOT
my EVC4 compiler :
> probably your environment is polluted by some PATH referring to
Vstudio2005 install folder :
> forget all of this : clean your PATH in any doubt, but my scripts do
refer to compiler location by explicit path.
>
>
> You will go nowhere in openssl for WCE unless you succeed, at first,
to recompile my V100a as I did.
>
> Regards
> Pierre
>
>
> Le 22/05/2014 14:33, ravi.vy...@gmail.com a �crit :
>> Hello Pierre.
>> I want To Build OPENSSL in WIN CE 6.0
>> WHat Change Require in .Bat Files.
>> HOw can I use your SSL CODE.?
>> How to Re-Compile Your Source Code.
>> I am Using Windows-XP
>> and visual studio 8.0.
>> I installed Microsoft eMbedded C++ 4.0.
>>
>> Whats Change are require
>>
>> _____________________________________
>> Sent from http://openssl.6102.n7.nabble.com

==========================
That said,

Now I have to say that you DO NOT follow my instructions while you should :

If you download everything from my webpage,
1/ you have to deal with my modified, ready to compile openssl V100A files.
Forget any other version of openssl for the moment.


2/ YOU MUST USE EVC4 compiler : I do NOT use VS2005 compiler and will
NOT give support with it (BECAUSE 1/ there are some differences between
compilation tools and options that I do NOT want to deal with, 2/ MS
VS2005 is expensive anyway (because vstudio express 2008/10/13 are not
able to compile for WCE)

I can help if you are following some basics so that we solve one problem
after the other.

But if you expect someone to help in your strange scenario of VS2005,
openssl 098, and WCE6 (indeed it is either WCE5 or WM6...), X86 target
then, do not expect any support all around...
sorry for that.

But, start with EVC4/ openssl V100a files/wcecompat that you will all
find on my http://delaage.pierre.free.fr page, ARMV4 target that you can
test on WM6.1.4 PRO emulators (free at MS),
which is a straightforward process thanks to the scripts I gave,
and then, when successful with that, give a try to go further..

NOTA :
As I said, I think I will issue a new compilable WCE version of the
1.0.2 latest snap of openssl in a few days....
that way you will save more time.

See you
Pierre Delaage



Le 22/05/2014 15:24, RaviVyas a �crit :

RaviVyas

unread,
May 23, 2014, 6:37:36 AM5/23/14
to
Hello Pierre DELAAGE,
Now i Am Following our Steps.
I Changed File makece.bat and wcedefs.bat file. also make a Chnage in Bat
File of WCEARMV4.
Title WCE ARMV4 Environment

MYBAT FILE IS:-

You are Setting Platform is
PLATFORM=STANDARDSDK
WHat is STANDARDSDK?

REM This batch file sets up an environment for building for a specific CPU
from the command line.
REM The build environment defaults to the Standard SDK for Windows CE .NET
platform. The macros that control the
REM platform are: PLATFORM, OSVERSION, WCEROOT and SDKROOT. The Standard SDK
for Windows CE .NET default settings
REM are as follows:
REM PLATFORM=STANDARDSDK
REM OSVERSION=WCE600
REM WCEROOT=C:\Windows CE Tools //Root dir for VCCE
REM SDKROOT=C:\Windows CE Tools //Root dir for Standard SDK for
Windows CE .NET
REM The batch file uses these macros to set the PATH, INCLUDE, LIB macros
for the default
REM platform. Please note that if the default setup options were altered
during
REM installation (for example, if the install directories were changed),
then the user needs
REM to modify these macros accordingly.

if "%OSVERSION%"=="" set OSVERSION=WCE600
if "%PLATFORM%"=="" set PLATFORM=STANDARDSDK
if "%WCEROOT%"=="" set WCEROOT=C:\Program Files\Microsoft eMbedded C++ 4.0
if "%SDKROOT%"=="" set SDKROOT=C:\Program Files\Microsoft SDKs..


The Customization of mywcebuild.bat

@echo off
:: created by pdelaage on 20100928
:: usage : makece ARMV4|X86|... other targets: see bat scripts in evc/bin
:: Note : adapt EVC/bin/WCE<target>.bat scripts
Title WCE COMPAT

:: !!!!!!!!!!!!!!
:: CUSTOMIZE THIS according to your EVC INSTALLED ENVIRONMENT
:: !!!!!!!!!!!!!!

set OSVERSION=WCE600
set PLATFORM=STANDARDSDK
set WCEROOT=C:\Program Files\Microsoft eMbedded C++ 4.0
set SDKROOT=C:\Program Files\Microsoft SDKs

:: !!!!!!!!!!!!!!!!!!
:: END CUSTOMIZATION
:: !!!!!!!!!!!!!!!!!!

:: Define TARGET CPU
:: -----------------


:: define "new" target (useful if one wants to compile for various WCE
target CPUs)
if "%1"=="" echo "USAGE : makece TARGETCPU other_make_options..."
if "%1"=="" echo
"TARGETCPU=(ARMV4|ARMV4I|ARMV4T|R4100|R4111|R4300|SH3|SH4|X86|X86EM|X86EMnset),
other cpu: see wcedefs.mak and bat scripts in evc/bin"
if "%1"=="" echo "do not hesitate to adapt this script for CPU and/or better
compilation flags!"
if "%1"=="" exit /B

:: old code to default to ARMV4, but it is better that users are WARNED that
the script now need an explicit target!
::if "%1"=="" set NEWTGTCPU=ARMV4

if NOT DEFINED TARGETCPU set TARGETCPU=XXXXX
if NOT "%1"=="" set NEWTGTCPU=%1
if NOT "%1"=="" shift

echo WCE TARGET CPU is %NEWTGTCPU%

rem Adjust MS EVC env vars
rem ----------------------

rem Check MSenv vars against our ref values

set isenvok=0
if "%NEWTGTCPU%"=="%TARGETCPU%" set /A "isenvok+=1"

if %isenvok%==1 echo WCE ENVIRONMENT OK
if %isenvok%==1 goto envisok

:: if env is NOT ok, adjust MS EVC env vars to be used by MS WCE<CPU>.BAT
:: (this is to avoid repetitive pollution of PATH)

echo WCE TARGET CPU changed
:: , destroying every obj files
:: no more if sep dirs del .\obj\*.obj
::if EXIST .\obj\%TARGETCPU% del .\obj\%TARGETCPU%\*.obj

:: if env is NOT ok, adjust MS EVC env vars to be used by MS WCE<CPU>.BAT
:: (this is to avoid repetitive pollution of PATH)

echo WCE ENVIRONMENT ADJUSTED

::call "C:\Program Files\Microsoft eMbedded C++
4.0\EVC\WCE600\BIN\WCEARMV4.BAT"
call "C:\Program Files\Microsoft eMbedded C++
4.0\EVC\WCE600\BIN\WCEARMV4.BAT"

set TARGETCPU=%NEWTGTCPU%
:envisok

::exit /B

rem make everything
rem ---------------

nmake /NOLOGO -f makefile %1 %2 %3 %4 %5 %6 %7 %8 %9


Is This Allright?
and WCEDEFS.mak File


# 20100928 pdelaage : PLATFORM is STANDARDSDK...

# Set WCEVERSION and WCELDVERSION
!IF "$(OSVERSION)"=="WCE200"
WCEVERSION=200
WCELDVERSION=2.00
!ELSEIF "$(OSVERSION)"=="WCE201"
WCEVERSION=201
WCELDVERSION=2.01
!ELSEIF "$(OSVERSION)"=="WCE210"
WCEVERSION=210
WCELDVERSION=2.10
!ELSEIF "$(OSVERSION)"=="WCE211"
WCEVERSION=211
WCELDVERSION=2.11
!ELSEIF "$(OSVERSION)"=="WCE212"
WCEVERSION=212
WCELDVERSION=2.12
!ELSEIF "$(OSVERSION)"=="WCE300"
WCEVERSION=300
WCELDVERSION=3.00
!ELSEIF "$(OSVERSION)"=="WCE420"
WCEVERSION=420
WCELDVERSION=4.20
!ELSEIF "$(OSVERSION)"=="WCE600"
WCEVERSION=600
WCELDVERSION=6.00
!ELSE
!ERROR Unexpected OSVERSION environment variable value
!ENDIF

# Set WCEPLATFORM to PLATFORM, with spaces replaced with underscores, and
uppercased
!IF "$(PLATFORM)"=="MS HPC"
WCEPLATFORM=MS_HPC
!ELSEIF "$(PLATFORM)"=="MS HPC Pro"
WCEPLATFORM=MS_HPC_PRO
!ELSEIF "$(PLATFORM)"=="ms palm size pc"
WCEPLATFORM=MS_PALM_SIZE_PC
!ELSEIF "$(PLATFORM)"=="ms pocket pc"
WCEPLATFORM=MS_POCKET_PC_2000
!ELSEIF "$(PLATFORM)"=="Pocket PC 2002"
WCEPLATFORM=MS_POCKET_PC_2002
!ELSEIF "$(PLATFORM)"=="STANDARDSDK"
WCEPLATFORM=STANDARDSDK
!ENDIF

# Set WCETARGETCPU, WCETARGETCPUDEFS and WCETARGETDEFS
WCETARGETDEFS=-DWCEPLATFORM=$(WCEPLATFORM)
!IF "$(TARGETCPU)"=="X86"
WCETARGETCPU=X86
WCETARGETCPUDEFS=-Dx86 -D_X86_
WCELDFLAGS=/nodefaultlib:oldnames.lib coredll.lib corelibc.lib
!ELSEIF "$(TARGETCPU)"=="X86EM" || "$(TARGETCPU)"=="X86EMnset CFG=none"
WCETARGETCPU=X86
WCETARGETCPUDEFS=-Dx86 -D_X86_
WCETARGETDEFS=$(WCETARGETDEFS) -D_WIN32_WCE_EMULATION
!ELSEIF "$(TARGETCPU)"=="SH3"
WCETARGETCPU=$(TARGETCPU)
WCETARGETCPUDEFS=-DSH3 -D_SH3_ -DSHx
!ELSEIF "$(TARGETCPU)"=="SH4"
WCETARGETCPU=$(TARGETCPU)
WCETARGETCPUDEFS=-DSH4 -D_SH4_ -DSHx
!ELSEIF "$(TARGETCPU)"=="R4100" || "$(TARGETCPU)"=="R4111" ||
"$(TARGETCPU)"=="R4300"
WCETARGETCPU=$(TARGETCPU)
WCETARGETCPUDEFS=-DMIPS -D_MIPS_ -DMIPS_R4000
!ELSEIF "$(TARGETCPU)"=="ARMV4" || "$(TARGETCPU)"=="ARMV4T" ||
"$(TARGETCPU)"=="ARMV4I"

WCETARGETCPU=ARM
WCETARGETCPUDEFS=-DARM -D_ARM_ -D_M_ARM -D$(TARGETCPU) -D_$(TARGETCPU)_
#pdelaage 20101020 , this is useless and NOT used anywhere! : WCECC=clarm
!ELSE

WCETARGETCPU=$(TARGETCPU)
WCETARGETCPUDEFS=-D$(TARGETCPU) -D_$(TARGETCPU)_
!ENDIF
WCETARGETDEFS=$(WCETARGETDEFS) $(WCETARGETCPUDEFS) -DUNDER_CE=$(WCEVERSION)
-D_WIN32_CE=$(WCEVERSION)

# Set CPU type for link
!IF "$(WCETARGETCPU)"=="X86"
#pdelaage 20101020: IX86 is for win32 desktop PC ! WCELDMACHINE=IX86
WCELDMACHINE=X86
!ELSE
WCELDMACHINE=$(WCETARGETCPU)
!ENDIF


and WCEARMV4.bat file

WCEARM4.BAT FILE PATH

set PATH=%WCEROOT%\COMMON\EVC\bin;%WCEROOT%\EVC\%OSVERSION%\bin;%path%
set
INCLUDE=%SDKROOT%\%OSVERSION%\%PLATFORM%\include\ARMV4;%SDKROOT%\%OSVERSION%\%PLATFORM%\MFC\include;%SDKROOT%\%OSVERSION%\%PLATFORM%\ATL\include;
set
LIB=%SDKROOT%\%OSVERSION%\%PLATFORM%\lib\ARMV4;%SDKROOT%\%OSVERSION%\%PLATFORM%\MFC\lib\ARMV4;%SDKROOT%\%OSVERSION%\%PLATFORM%\ATL\lib\ARMV4;

There is Not any Directory Structure like This.
set INCLUDE=%SDKROOT%\%OSVERSION%\%PLATFORM%\include\ARMV4
VS.....
C:\Program Files\Microsoft SDKs\*WCE600\STANDARDSDK\include\ARMV4*


In C:\Program Files\Microsoft SDKs Directory Structure
+windows
--v5.0
--v6.0A






--
View this message in context: http://openssl.6102.n7.nabble.com/OPENSSL-for-windows-mobile-5-6-tp38606p50251.html

Pierre DELAAGE

unread,
May 23, 2014, 1:17:26 PM5/23/14
to
Hello,
In the scripts, you only have to tweak :
1/ the "CUSTOMIZE" block (line 12 to 15)
2/ the WCECOMPAT path (line 60)

AND NOTHING ELSE : so you can remove all your stuff about WCE600 which
is completely IRRELEVANT.

STANDARDSDK is just the name of one of the subfolders in MS SDK
installation, referring to an SDK suited for WCE5/WM6.

YOU MUST DO AS I STATED on my webpage and install the WCE420 :

presently, we just DON'T care about your WM6 target (WCE6 just DOES NOT
exist ! this is just the second time I say that...).

so ...live OSVERSION and PLATFORM as they are....

Forget your present concern about WM6 ( W-M-6 ....not W-C-E-6 !
understood ?),
JUST TRY to install and recompile my V100a stuff, (EVC4+sp4) tools+
WCE420 SDK.

then MY wcecompat stuff (which is ready to compile provided you have
correctly installed ms tools and sdk and tweaked some bat script).


For wcecompat / wcedefs.mak : DO NOT CHANGE ANYTHING THERE ! forget your
"WCE600" stuff. go back to my file.

For the SDK / .

WCEARMV4.bat....

....Well, ok, in fact it is better that you let it as it IS ! either
keeping the original one of MS, or mine,
BUT DO NOT CHANGE ANYTHING in it !


Got it ?

See you
Pierre




Le 23/05/2014 12:37, RaviVyas a �crit :

RaviVyas

unread,
May 23, 2014, 8:23:44 AM5/23/14
to
hello sir,
i am done with my WCECompat and gets the libs.
now when building Openssl 0.9.8i i got an error like this.

Building OpenSSL
perl util/copy.pl ".\crypto\buildinf.h" "tmp32dll_ARMV4I\buildinf.h"
Copying: ./crypto/buildinf.h to tmp32dll_ARMV4I/buildinf.h
perl util/copy.pl ".\crypto\opensslconf.h"
"inc32\openssl\opensslconf.h"

Copying: ./crypto/opensslconf.h to inc32/openssl/opensslconf.h
link /nologo /opt:ref /subsystem:windowsce,6.00 /machine:THUMB /dll
/out
:out32dll_ARMV4I\libeay32.dll /def:ms/LIBEAY32.def
@C:\Users\kits\AppData\Local\
Temp\nm4532.tmp
LIBCMT.lib(strnicmp.obj) : fatal error LNK1112: module machine type 'X86'
confli
cts with target machine type 'THUMB'
NMAKE : fatal error U1077: '"C:\Program Files (x86)\Microsoft Visual Studio
9.0\
VC\ce\bin\x86_arm\link.EXE"' : return code '0x458'
Stop.

please help me out

Thank you



--
View this message in context: http://openssl.6102.n7.nabble.com/OPENSSL-for-windows-mobile-5-6-tp38606p50255.html

Ravi vyas

unread,
May 26, 2014, 4:58:12 AM5/26/14
to
Thanks,
I sucessFull All The Steps Which You Given To ME.
Now My Next Target To Build For Windows Mobile 6.0 SDK.
But The Problem is That. In Windows Mobile 6.0 SDK only 4 Folder
1)Lib
2)Include
3)Device Emulation
4)DeviceemulationV650 .
So I can I Set Path For atl and mfc Folders Path.
ok
In NExt Include Directory Only 1 Folder is There ARMV4i
so How Can These Steps Performed.



Sent from the OpenSSL - Dev mailing list archive at Nabble.com.
______________________________________________________________________
OpenSSL Project                                 http://www.openssl.org
Development Mailing List                       opens...@openssl.org
Automated List Manager                           majo...@openssl.org


______________________________________________________________________
OpenSSL Project                                 http://www.openssl.org
Development Mailing List                       opens...@openssl.org
Automated List Manager                           majo...@openssl.org



--
Thanking You.
Ravi Vyas...

Pierre DELAAGE

unread,
May 26, 2014, 6:03:58 AM5/26/14
to
Good,
Unless you ABSOKUTELY need some services that is in the WM6 SDK and NOT in WCE420 SDK,
I recommend that you continue to play with your installation of WCE420 SDK and evc4 compiler.

Now you have built YOUR openssl V100a lib I guess.

Is it working with YOUR application on a WM6 emulator or phone ?

it should, because using my compilation tools with WCE420 SDK, my apps were running perfectly on WM6 phones.

As I said, in the next days I will re-submit some compilation patch to openssl V102 most recent snapshot. please be patient if you need some recent WCE port of openssl.

For the future, I cannot help with Visual Studio 2005 and its embedded SDK for WCE, I am sorry : I do not have this tool.
I checked some docs on internet and now I understand why you referred so frequently to "WCE600":
it is something that is only meaningful inside VS2005.

But, anyway, be sure that everything you will compile with evc4 compiler + WCE420 SDK will work on WM6 (and I really say "WM6") phones :
no problem.

Because, in the complicated MS world, WM6 refers to "real phones" while WCE600 refers to an embedded version of the WCE SDK inside Visual Studio 2005.

Forget this for the moment, and try to build YOUR APPLICATION with YOUR V100a openssl lib.

For your app : provided that you refer to the right openssl includes in your makefile, and link to the right openssl lib,
you can build your app EITHER with evc4/SDK420 or your VS2005/WCE600 sdk.

Regards
Pierre

RaviVyas

unread,
May 26, 2014, 7:28:04 AM5/26/14
to
Hello Pierre,
Thanks For Nice Guidance.
I Suceessed To BUILD OpenSSL Lib for ARMV4 and ARMV4I

*ARMV4*
libeay32.dll
libeay32.lib

ssleay32.dll
ssleay32.lib

*ARMV4I*
libeay32.dll
libeay32.lib

ssleay32.dll
ssleay32.lib
Thats Task Has Been Done.
Now Can I USe This .lib And .dll in MyEmulator.

IS it need To Put Both Lib puts in Myproject Folder?
1)wcecompat.lib
2)wcecompatex.lib

Which Installation is Require in MY Emulator.?



--
View this message in context: http://openssl.6102.n7.nabble.com/OPENSSL-for-windows-mobile-5-6-tp38606p50314.html

Pierre DELAAGE

unread,
May 26, 2014, 9:07:59 AM5/26/14
to
Ok, good again
For execution time, when all is done with your app,
you do NOT need wcecompat NOR wcecompatex,
because those lib are STATIC libraries, that are now "put inside" your dll.

You noticed that your compilation of wcecompat DID NOT produce any dll,
just libs.
Those lib have been statically liked inside the openssl dll.

So, for execution : just put the two dll on the same folder in the
emulator as your app.

To do that, I hope that you have understood that there is a SHARED
folder between your emulator file system, and your PC file system.
In the emulator window, see "File/Configure/General/Shared folder" for
that.

I guess you are aware of that if you have already played with the
emulator...

From a development point of view:
In vstudio you have to instruct vstudio where to find your DYNAMIC libs
"libeay32.lib ssleay32.lib "
for linking step when building your app.

I have little knoweldege of various versions of Vstudio (in French...),
unfortunately not 2005...,
check that :
Tools / Options / Project and solutions/ Directories of VC++/
in the top right drop-down list, select "include files" to point to
openssl includes folder,
and "library files" to point to the folder containing your openssl fresh
libs.

In the makefile, refer to the two DYNAMIC libs : libeay32.lib ssleay32.lib
See Project menu/properties/Configuration properties or
settings/Linker/Input
/ extra dependencies.

Sorry for my approximate english translation of French VS menus...but
you should already know all of these things.

Personnally, I prefer to play with good old makefiles...

Regards
Pierre



Le 26/05/2014 13:28, RaviVyas a �crit :

parthd...@gmail.com

unread,
Mar 5, 2018, 9:36:52 AM3/5/18
to
Hello,

Can you please send compiled libeay32.lib & ssleay32.lib for ARM4I on my mail id parthd...@gmail.com ?
Please !
Reply all
Reply to author
Forward
0 new messages