-
Notifications
You must be signed in to change notification settings - Fork 186
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
chromium 103 does not build for imx8qm #649
Comments
I am seeing the same issue building chromium-ozone-wayland for wayland only for i.MX8MM after applying the same patch. | aarch64-poky-linux-ld.lld: error: undefined symbol: gl::NativeViewGLSurfaceEGL::NativeViewGLSurfaceEGL(gl::GLDisplayEGL*, void*, std::__1::unique_ptr<gfx::VSyncProvider, std::__1::default_deletegfx::VSyncProvider >) |
The immediate problem is that from #elif defined(__GBM__)
typedef void *EGLNativeWindowType;
...
#elif defined(USE_OZONE)
typedef intptr_t EGLNativeWindowType; the first branch is used for some sources while the second one for other. This changes C++ function signatures. |
setting
workarounds it for me. |
Hello, I had exactly the same issue (but with chromium 105 build) and I have chosen the opposite approach. Index: imx-gpu-viv-6.4.3.p2.0-aarch64/gpu-core/usr/lib/pkgconfig/gbm.pc
===================================================================
--- imx-gpu-viv-6.4.3.p2.0-aarch64.orig/gpu-core/usr/lib/pkgconfig/gbm.pc
+++ imx-gpu-viv-6.4.3.p2.0-aarch64/gpu-core/usr/lib/pkgconfig/gbm.pc
@@ -8,4 +8,4 @@ Description: vivante gbm library
Version: 17.2
Libs: -L${libdir} -lgbm
Libs.private: -ldl
-Cflags: -I${includedir} -DLINUX -D__GBM__
+Cflags: -I${includedir} -DLINUX |
Building for imx8mp, having the same issue. Any consensus on whether it needs fixing in chromium or imx-gpu-viv? |
@Villemoes What I can assert is that chromium does not seem to use GPU acceleration with my method. I have to check if it behaves better with open source drivers. |
Howdy, I'm trying to get Chromium compiled for Dunfell Yocto for an iMX8X and am hitting this error. Which file did you add the Edit: Might have figured it out; I put it at the bottom of |
We have been stuck on chromium 92 on i.MX8QM for a while but I copied this recipe from NXP's meta-imx layer: Seems to work, with GPU acceleration, gets us to chromium 101 at least. I'm using with commit 6079a8b of meta-browser for chromiums 101 recipe. |
What about hardware video decode? |
I haven't tried hardware video decode but a commit says it was added: commit fe0d3587d905a8fa32a9830d177f97c90352fdc5
|
Wow, that's very timely. I will check it out. Thank you. |
You tested on Langdale, Kirkstone or Dunfell? |
Is the patchset public? |
I've found this to be a somewhat smaller hammer diff --git a/ui/gl/BUILD.gn b/ui/gl/BUILD.gn
index 761888bf4a540..0d31ab3b34f35 100644
--- a/ui/gl/BUILD.gn
+++ b/ui/gl/BUILD.gn
@@ -260,6 +260,13 @@ component("gl") {
if (angle_shared_libvulkan && !is_chromeos) {
data_deps += [ "//third_party/vulkan-deps/vulkan-loader/src:libvulkan" ]
}
+ defines += [ "WAYLAND_GBM" ]
+
+ deps += [
+ "//third_party/minigbm",
+ "//ui/gfx:memory_buffer",
+ "//ui/gfx/linux:gbm",
+ ]
}
} |
One of the changes chromium 114 brought in was 20f14755 "ui: gbm_wrapper: Ensure to create BOs with |
The imx gbm library hardcodes dri device nodes but still implements the calls to request them. This patch allows chrome to ignore the ones returned in favor of env vars.
|
Yes, reverting those commits worked for me as well. |
Hello to everybody, |
Confirm for 123 version. After make all patches from meta-browser applicable (or remove such backport). Pathces from meta-imx doesn't help. |
It seems NXP attempted to patch this twice. First in meta-imx commit nxp-imx/meta-imx@45ae537 with the comment " Disable VPU temporarily until the patches are rebased based on newer version of chromium". Then they reverted that in commit 5401bc9. Next, they renamed the top level folder "meta-sdk" to "meta-sdk-imx", so the commit history is hard to follow. Now NXP's chromium patches are here: https://github.com/nxp-imx/meta-imx/tree/nanbield-6.6.3-1.0.0/meta-imx-sdk/dynamic-layers/chromium-browser-layer/recipes-browser/chromium/chromium-ozone-wayland. It appears that these 3 patches are the relevant ones: I've got a build chugging now to see if they resolve this issue |
Building chromium-ozone-wayland on i.MX8QM for wayland only, no x11 libs. Have the following patch to disable dri:
Similar patch worked for 101, but in 103 I'm getting a compilation error:
The text was updated successfully, but these errors were encountered: