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
Le 26/05/2014 10:58, Ravi vyas a écrit :
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.
On Fri, May 23, 2014 at 10:47 PM, Pierre DELAAGE
<delaage.pie...@free.fr <mailto:delaage.pie...@free.fr>> wrote:
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 :
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
Sent from the OpenSSL - Dev mailing list archive at Nabble.com.
______________________________________________________________________
OpenSSL Project http://www.openssl.org
Development Mailing List openssl-dev@openssl.org
<mailto:openssl-dev@openssl.org>
Automated List Manager majord...@openssl.org
<mailto:majord...@openssl.org>
______________________________________________________________________
OpenSSL Project http://www.openssl.org
Development Mailing List openssl-dev@openssl.org
<mailto:openssl-dev@openssl.org>
Automated List Manager majord...@openssl.org
<mailto:majord...@openssl.org>
--
*Thanking You.*
*Ravi Vyas...*
