Open rwmacleod opened 2 years ago
Adding wayland to DISTRO_FEATRES seems to have resolved the build error (at ~85% now, failed earlier without) but I'd like to see why it's required now and hasn't been required in earlier releases. We could add a REQUIRED_DISTRO_FEATURE to the chromium-x11 recipe but I'm reluctant to do that for/to the old branches.
Later... yes that builds.
Do you mean this is a chromium-x11 build that's failing because the Wayland headers aren't present during the build?
Yes, which is a little odd. Btw, adding vulkan and wayland avoids the problem.
cc @msisov do you know what the situation is upstream? Do we just need to depend on the headers for the build?
Any update on this?
@rwmacleod @Oquirella can you check if #678 that I just merged fixes the issue for you?
I will check but not until next week at the earliest.
In a non-poky distro using the kirkstone branch, without wayland or vulkan included in DISTRO_FEATURES, I'm seeing:
I'm adding wayland to DISTRO_FEATURES to confirm that that is the significant difference from all of the successful builds I did with poky which has: POKY_DEFAULT_DISTRO_FEATURES = "largefile opengl ptest multiarch wayland vulkan" in all of dunfell, kirkstone, master.