Hello,

I have ElevateDB LCL Standard 2.02 b 11 with Source (Win32, WinCE) installed on default instalation directory:

c:\Program Files\ElevateDB LCL Standard with Source\Version 2\Lazarus (Win32) 0.926\..
and
c:\Program Files\ElevateDB LCL Standard with Source\Version 2\Lazarus (WinCE) 0.926\..

Win32 version I have installed by install edb202l0926design.lpk package. I try simple EDB project in Win32 enviroment and all working
all right. I have installed cross-arm-wince-win32 extension of Lazarus. Project without EDB is possible to cross compile to WinCE/ARM
platform but when I try to cross-compile project with EDB compilation failed with
error messages:

C:\Program Files\ElevateDB LCL Standard with Source\Version 2\Lazarus (Win32) 0.926\code\source\edbenv.pas(330,22) Error:
Identifier not found "EnumSystemLocalesA"
C:\Program Files\ElevateDB LCL Standard with Source\Version 2\Lazarus (Win32) 0.926\code\source\edbenv.pas(425,46) Error:
Identifier not found "GetCurrentDirectoryA"
C:\Program Files\ElevateDB LCL Standard with Source\Version 2\Lazarus (Win32) 0.926\code\source\edbenv.pas(436,38) Error:
Identifier not found "GetTempPathA"
C:\Program Files\ElevateDB LCL Standard with Source\Version 2\Lazarus (Win32) 0.926\code\source\edbenv.pas(447,45) Error:
Identifier not found "GetSystemDirectoryA"
C:\Program Files\ElevateDB LCL Standard with Source\Version 2\Lazarus (Win32) 0.926\code\source\edbenv.pas(491,44) Error:
Identifier not found "GetModuleFileNameA"
C:\Program Files\ElevateDB LCL Standard with Source\Version 2\Lazarus (Win32) 0.926\code\source\edbenv.pas(503,28) Error:
Identifier not found "GetComputerNameA"
C:\Program Files\ElevateDB LCL Standard with Source\Version 2\Lazarus (Win32) 0.926\code\source\edbenv.pas(515,24) Error:
Identifier not found "GetUserNameA"
C:\Program Files\ElevateDB LCL Standard with Source\Version 2\Lazarus (Win32) 0.926\code\source\edbenv.pas(558) Fatal: There
were 9 errors compiling module, stopping

I know that problem is using Win32 version of EDB runtime package in WinCE/ARM settings of compiler. What is need to change in
configuration of Lazarus to use WinCE version of EDB in WinCE/ARM cross-compiller?

Regards

Zdenek Jaburek

Zdenek,

<< I know that problem is using Win32 version of EDB runtime package in
WinCE/ARM settings of compiler. What is need to change in configuration of
Lazarus to use WinCE version of EDB in WinCE/ARM cross-compiller? >>

What you need to do is make sure that your compiler search path is changed
so that it is pointing to the WinCE source code for ElevateDB instead of the
Win32 source code for ElevateDB.  To do so, modify the compiler path
settings here (0.926):

Project/Compiler Options/Paths

In the Other Unit Files edit box, enter the search path to the WinCE source
code.  In the Include Files edit box, do the same thing (same path).  If you
check the compiler options now via the Show Options button at the bottom of
the dialog box, you will see that these paths are now used *before* the
existing runtime package paths, so that the WinCE units will be used instead
of the Win32 units.  When you want to switch back to using the Win32 units,
just remove the path from these two edit boxes.

--
Tim Young
Elevate Software
www.elevatesoft.com

Hello Tim,

thank you for your help. Just now I do compile project with EDB fo wince/arm platform.

Another question - in simple project I try connect to remote server via EDBSession. In win32/i386 is working correctly but in wince/arm obtain
error 'ElevateDB Error #1100 A connection to the server .. cannot be established'. I tested this on Device emulator with Windows Mobile 6
Proffesional image and HP iPAQ 214 with the same result. Ping from Device emulator and iPAQ is ok. Is connecting to the remote server usable in
wince at this moment?

Regards

Zdenek


"Tim Young [Elevate Software]" wrote:

Zdenek,

<< I know that problem is using Win32 version of EDB runtime package in
WinCE/ARM settings of compiler. What is need to change in configuration of
Lazarus to use WinCE version of EDB in WinCE/ARM cross-compiller? >>

What you need to do is make sure that your compiler search path is changed
so that it is pointing to the WinCE source code for ElevateDB instead of the
Win32 source code for ElevateDB.  To do so, modify the compiler path
settings here (0.926):

Project/Compiler Options/Paths

In the Other Unit Files edit box, enter the search path to the WinCE source
code.  In the Include Files edit box, do the same thing (same path).  If you
check the compiler options now via the Show Options button at the bottom of
the dialog box, you will see that these paths are now used *before* the
existing runtime package paths, so that the WinCE units will be used instead
of the Win32 units.  When you want to switch back to using the Win32 units,
just remove the path from these two edit boxes.

--
Tim Young
Elevate Software
www.elevatesoft.com

Zdenek,

<< Another question - in simple project I try connect to remote server via
EDBSession. In win32/i386 is working correctly but in wince/arm obtain error
'ElevateDB Error #1100 A connection to the server .. cannot be established'.
I tested this on Device emulator with Windows Mobile 6 Proffesional image
and HP iPAQ 214 with the same result. Ping from Device emulator and iPAQ is
ok. Is connecting to the remote server usable in wince at this moment? >>

I'll have to double-check, but it should work okay.  I'll let you know what
I find out.

--
Tim Young
Elevate Software
www.elevatesoft.com

Zdenek,

I just wanted to let you know that I didn't forget about you.  I'm holding
off 2.02 B12 until this evening when I can double-check this for you and
make sure that the connections are working properly for the WinCE support.

--
Tim Young
Elevate Software
www.elevatesoft.com

Zdenek,

Okay, here's the deal.  There appears to be a bug in the winsock.pp unit
that is affecting basic Winsock functionality under Windows CE.  I've
submitted a bug report along with the fixes here:

http://bugs.freepascal.org/view.php?id=13614

If you implement the fixes in the respective FPC winsock.pp unit for the
Windows CE/ARM RTL, then you will be all set and the connectivity should
work just fine from Windows CE to an EDB Server.

I'm using the bleeding-edge Lazarus 0.9.27 / FPC 2.2.5 available from the
daily snapshots for my tests here.

There's also an issue with the SysErrorMessage function from the sysutils.pp
unit for Windows CE that I'm looking into.

--
Tim Young
Elevate Software
www.elevatesoft.com