Thank you for the hint. It led me to the source of the problem,
which was libepoxy.
It looks that after changing configuration
(DISTRO_FEATURES_remove = " x11"), SSTATE was still populating
sysroot of gtk+3 with the older version of libepoxy configuration
file (*.pc) creating dependency to 'gl' and 'x11'. In my case I
had to call:
bitbake -c cleanall libepoxy
bitbake -c cleanall gtk+3
In order to avoid such issues in the future, is there any way to
force bitbake (after such considerable configuration change like
modification of DISTRO_FEATURES) to rebuild sysroot for each
recipe if necessary instead of grabbing them from the cache ? I
know, one could delete sstate-cache directory, but obviously it
will enormously increase rebuild time. I have been wondering
whether there is an intermediate solution.
On 09.11.2020 15:28, Alexander Kanavin wrote:
Do you actually need gtk+3 in your image?
There is a poky configuration that builds core-image-weston
without x11, and core-image-weston does pull in gtk+3, and all
that happens without errors:
so I'd suggest you reproduce that, get it to build, then
investigate where your build diverges.
I am building an image based on core-image-weston.
I would like to use only wayland backend, thus I defined
in my machine's configuration:
DISTRO_FEATURES_append = " wayland"
DISTRO_FEATURES_remove = " x11"
I have a problem with build of gtk+3:
| checking for pango pangocairo gdk-pixbuf-2.0 >=
2.30.0 cairo >= 1.14.0 cairo-gobject >= 1.14.0
gio-unix-2.0 >= 2.53.4 wayland-client >= 1.9.91
wayland-protocols >= 1.12 xkbcommon >= 0.2.0
wayland-cursor >= 1.9.91 wayland-egl cairo epoxy
>= 1.4 fribidi >= 0.19.7... no
| configure: error: Package requirements (pango
pangocairo gdk-pixbuf-2.0 >= 2.30.0 cairo >=
1.14.0 cairo-gobject >= 1.14.0 gio-unix-2.0 >=
2.53.4 wayland-client >= 1.9.91 wayland-protocols
>= 1.12 xkbcommon >= 0.2.0 wayland-cursor >=
1.9.91 wayland-egl cairo epoxy >= 1.4 fribidi
>= 0.19.7) were not met:
| Package 'x11', required by 'gl', not found
The configuration flags in config.log seems to be ok:
$ ../gtk+-3.24.8/configure --build=x86_64-linux
--prefix=/usr --exec_prefix=/usr --bindir=/usr/bin
--disable-glibtest --disable-xinerama --enable-modules
--disable-colord --disable-gtk-doc --disable-static
--disable-cups --disable-glx --enable-opengl
Has anybody else experience similar issue? Do you know a
fix? I work with the latest zeus