forked from enlightenment/efl
evas-modules affects evas engine modules if they are static or shared, but ecore evas modules are still modules... so all in all this doesnt help much as it still requires modules to be separate from the shared libs, thus disallowing for statically linking efl into an app anyway etc. etc. etc. ... so less options to deal with, less complexity. better.devs/bu5hm4n/dead_events
parent
15696f5e7c
commit
6d8e39a642
16 changed files with 100 additions and 170 deletions
Loading…
Reference in new issue