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 WinCE (at least on my device) wants the user to ACK the
untrusted code. But the warning isn't displayed properly as evas/ecore
already took the screen. As a quick workaround I disabled the security
check. But for the future this isn't a real option...
The second problem is a real one! In
evas/src/modules/engines/software_16_wince/evas_engine.c the setup()
function configures the output Render_Engine. If the function fails to
setup the chosen rendering backend it frees the Render_Engine and leaves
e->engine.data.output with uninitialized data. AFAIK there is no way to
inform the caller...
>> 2. Evas engine modules aren't named properly by default. (e.g.
>> module.dll instead of software_16_wince.dll)
>
> indeed, but I've put a script in the wiki that creaates for you a zip
> files and which renames the names of the modules
Is there a reason to keep it like that?? I've fixed the Makefile.am
files here. Works fine for me.
Klaus
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
enlightenment-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
