Hello,
I just found out that now all modules (I checked Evas/Ecore_Evas) in
EFL are linked static into the libs.
Is it possible to configure EFL trunk in a way to compile modules as
shared objects? Or is static the only supported way?
I ask this because of some reasons:
The module loader code is still present. So I assume it should be
possible to configure. I ported the module loader to Android, but now
from out of the box it wasn't needed to run the linked modules.
So good so far, but...
I created a new ecore_evas engine (copy&paste from other one). And now I
get a module and not linked static for this. No idea where to configure
this. Any hints? How ever, this is minor important as I have the module
loader...
Second there're lot of stuff compiled static that I don't need (e.g.
various file formats). With module design I could just not copy it into
my application and that's it. Now I couldn't even disable it. Is this
really needed? It just increases code size on embedded devices.
Yes, yes, who cares on Android, but I hate waste of memory and
flash... :-)
regards
Andreas
--
Technical Blog <http://andreasvolz.wordpress.com/>
------------------------------------------------------------------------------
Free Next-Gen Firewall Hardware Offer
Buy your Sophos next-gen firewall before the end March 2013
and get the hardware for free! Learn more.
http://p.sf.net/sfu/sophos-d2d-feb
_______________________________________________
enlightenment-devel mailing list
enlightenment-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
