You are not logged in.
Pages: 1
I try to compile the client from sample 4 (http client server) in Lazarus for Wince. The compiler stops in file synzip by this line
{$ifndef ANDROID}
clocale,
{$endif}
Are there rules to use mORMot on WinCE?
Has anyone mORMot working on WinCE?
Offline
We never try to compile for WinCE yet...
AFAIR no one did...
So I guess that you won't be able to compile the main framework trunk to WinCE.
But I think that you may be able to use the SynCrossPlatform*.pas units for WinCE.
They allow to connect to a mORMot server, and create most client code with wrapper.
See http://synopse.info/files/html/Synopse% … ml#TITL_86
Offline
I could build a client for WinCE/ARM using fpc 2.6.4 using the crossplatform-code generated by a mORMot server.
Server was interface-based/records-only.
Had some problems with UTF-8 conversion in TextToHttpBody and HttpBodyToText ('?' for umlauts) and changed the conversion to an implicit cast (if at all, i don't know)
//instead of Text := Utf8Decode(utf8)
Text := utf8;
Hope this helps!
Offline
AFAR did Zeos run in trouble on WinCE because FPC uses the $UNICODE define to indicate a Unicode plattform instead of a Unicode-IDE.
No idea if this issue still remains or if MarcoVV replaced the defines.
@sevo did you try to comile Zeos on WinCE?
Offline
@sevo did you try to comile Zeos on WinCE?
no
Offline
Pages: 1