Hi,

after quite a big amount of work we have successfully landed this morning a update to our build system which enables to build efl as a single big .so instead of multiple seperated .so's. The layout is that every single .so is merged into efl-one.so except: - eolian: no normal app would benefit from it, and it would make our build *a lot* more complex - ecore_avahi: there is no real user for this within efl, in general i dont think anyone is going to benefit from it
- efl_canvas_wl: This is also not beneficial to a standard efl application
- elua: This is only for bindings.
- ecore_drm / wayland : These are deprecated libs, not to confuse with ecore_wl2 / ecore_drm2, which is included in efl-one
- exactness: Not useful for a normal efl app.

To build efl-one you need to pass: "-Defl-one=true" to meson. After this is done, additionally to all the smaller libs, efl-one.so will be build. The modules of ecore / evas etc. and all the binaries will link to efl-one.so not to the smaller libraries. However, for compatibility reasons, and complexity reasons, the small .so's are still build and installed.

If you have an app that you want to test out with efl-one: There is now a efl-one.pc file installed, which can be used to link to the correct libraries, no other efl dependency is then required.

From some early profiling: this saves ~1MB of memory when running a efl app, i have so far not tested out what impact it has on runtime performance or first frame numbers.

greetings,
   bu5hm4n



_______________________________________________
enlightenment-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/enlightenment-devel

Reply via email to