forked from enlightenment/efl
Carsten Haitzler
9371cdfef8
so the evas modules able to be static or not was a bit pointless as it could inline all evas modules (or none) not just the most common or not, but ecore evas modules were still modules, so it really wasn't being useful. image loaders ans savers omn the other hand were *ALL* being statically built in without exception. this was kind of a regression in the build system in the move to meson. some were static due to micro optimizations and performance inlining the most common to save a little extra loading + linking + page fragmentation for loaders you are likely to need in most cases as well as save the drity pages from linking in their dependencies (libgif, libtiff, libwebp and all their dependencies too etc. etc.). this now brings back the ability to decide which are static and which are shared modules (not exposed to the user as options for meson - fixed in meson.build files which i think is good enough given the purpose of this). |
||
|---|---|---|
| .. | ||
| benchmarks | ||
| bin | ||
| bindings | ||
| edje_external | ||
| examples | ||
| generic | ||
| lib | ||
| modules | ||
| scripts | ||
| static_libs | ||
| tests | ||
| wayland_protocol | ||