forked from enlightenment/efl
elementary: when building with backends, we apparently need to link with them to.
This make elementary break the modularity of the underlying layer. I haven't looked at what is going on here, but basically if you have a wayland, a drm, whatever backend turned on. You need elementary to be link against that ecore_* directly. This means we are lacking in abstraction in Ecore_Evas and are dlopening to much library at startup. This needs to be improved in the future. I am guessing this is related to maybe DnD and C&P.
This commit is contained in:
parent
3b9f53317d
commit
ab4bfcf250
|
@ -5139,9 +5139,9 @@ EFL_INTERNAL_DEPEND_PKG([ELEMENTARY], [eo])
|
|||
EFL_INTERNAL_DEPEND_PKG([ELEMENTARY], [efl])
|
||||
EFL_INTERNAL_DEPEND_PKG([ELEMENTARY], [evas])
|
||||
EFL_INTERNAL_DEPEND_PKG([ELEMENTARY], [ecore])
|
||||
EFL_OPTIONAL_INTERNAL_DEPEND_PKG([ELEMENTARY], [${want_x11_any}], [ecore_x])
|
||||
EFL_OPTIONAL_INTERNAL_DEPEND_PKG([ELEMENTARY], [${want_wayland}], [ecore_wl2])
|
||||
EFL_OPTIONAL_INTERNAL_DEPEND_PKG([ELEMENTARY], [${build_ecore_evas_x11}], [ecore_x])
|
||||
EFL_OPTIONAL_INTERNAL_DEPEND_PKG([ELEMENTARY], [${want_drm}], [ecore_drm])
|
||||
EFL_OPTIONAL_INTERNAL_DEPEND_PKG([ELEMENTARY], [${build_ecore_evas_wayland}], [ecore_wl2])
|
||||
EFL_INTERNAL_DEPEND_PKG([ELEMENTARY], [ecore-evas])
|
||||
EFL_INTERNAL_DEPEND_PKG([ELEMENTARY], [ecore-file])
|
||||
EFL_INTERNAL_DEPEND_PKG([ELEMENTARY], [ecore-input])
|
||||
|
|
Loading…
Reference in New Issue