chromium-ozone-wayland: add virtual/libgbm to DEPENDS#988
chromium-ozone-wayland: add virtual/libgbm to DEPENDS#988Ashwin-Prabhakar wants to merge 1 commit into
Conversation
lumag
left a comment
There was a problem hiding this comment.
Please provide details in the commit message, what / how it is failing. I assume that the lack of the GBM would have been an issue that should have been detected already.
| DEBUG: Python function extend_recipe_sysroot finished is the build failure I see. |
|
@Ashwin-Prabhakar you've posted the log rather than the explanation. And it's not a part of the commit message. From my point of view, you still need to explain, what is going on (e.g. virtual/egl isn't required to depend / provide virtual/libgbm thus in the ... build configuration ... happens). |
@lumag I have updated the commit message incorporating your review comments. Please check and let me know if it is to your satisfaction. |
lumag
left a comment
There was a problem hiding this comment.
What is In the current build configuration,?
bitbake -e chromium-ozone-wayland | grep -E '^PREFERRED_PROVIDER_virtual/(egl|libgbm|libgl)'" This is in my current build configuration. |
And how does one guess it from your commit message? |
…tups The Chromium Ozone Wayland backend relies on minigbm, which executes a pkg-config check for 'gbm' during the configure task. In the current build configuration, virtual/egl is provided by libglvnd. Unlike some monolithic vendor graphics drivers, libglvnd only acts as a vendor-neutral dispatch layer and does not provide or implicitly pull in GBM headers or libraries. As a result, 'gbm.pc' is missing from the recipe sysroot, causing the GN build configuration to fail. Explicitly adding virtual/libgbm to DEPENDS ensures that the necessary GBM pkg-config files are populated into the Chromium recipe sysroot regardless of the chosen EGL provider. Signed-off-by: Ashwin Prabhakar <ashwin.prabhakar@qti.qualcomm.com>
Thanks, I have updated the commit message. |
Add virtual/libgbm to DEPENDS to fix a build failure caused by missing GBM headers or libraries when compiling the Chromium Ozone Wayland backend.