On Tue, 2 Dec 2008, Klaus Rechert wrote:
> Got everything working now :) ! I could identify two problems. One is the
> late loading/binding of evas modules. As these modules aren't trusted WinCE
> (at least on my device) wants the user to ACK the untrusted code. But the
> warning isn't displa
Hi,
>> I've tried to get your EFL example working on several WinCE devices.
>> No success with the precompiled binaries.
>
> what are the problems ?
Got everything working now :) ! I could identify two problems. One is
the late loading/binding of evas modules. As these modules aren't
trusted W
On Mon, 1 Dec 2008, Klaus Rechert wrote:
> Hi,
>
> I've tried to get your EFL example working on several WinCE devices. No
> success with the precompiled binaries.
what are the problems ?
> So I compiled the libs with debugging
> symbols and stumbled upon few issues:
>
> 1. Evas needs ddraw.
The trace below was made with wince_gapi. With wince_fb the trace looks
different but it seems to crash on a similar issue.
warning: ecore_wince : instance + class bon
warning: *** ecore message : create 240 320
Error while mapping shared library sections:
oleaut32.dll: No such file or directory
Hi,
I've tried to get your EFL example working on several WinCE devices. No
success with the precompiled binaries. So I compiled the libs with
debugging symbols and stumbled upon few issues:
1. Evas needs ddraw.h to compile evas_wince_ddraw_buffer.cpp. It is not
catched by configure.
2. Evas
