if your platform is picky enough it won't want to leave unresolved
symbols (which wshould be resovled at runtime from the host lib) so we
need to link these modules to evas. the problem is due to the
complicated build of some modules being static and some shared, evas
is declared with evas_goal and this has to be declared after static
modules are declared but since i was declaring static and shared at
the same time from a table this breaks. so i have to move all the
static and shared module stuff into evas_goal into 2 phases. one phase
for the static and one for the shared after evas is delcared so evas
as a target exists to link to.
Gbp-Pq: Name 0005-build-images-loaders-and-saver-modules-need-to-link-.patch
Origin: other
Forwarded: no
Last-Update: 2019-12-24
edje.pc gets its lua Requies entry from -Dlua-interpreter. But it
should get the appropriate versioned entry instead.
Last-Update: 2019-12-24
Gbp-Pq: Name 25_edje_check_luaold.diff