-
Notifications
You must be signed in to change notification settings - Fork 132
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
Add Yocto support #30
Comments
Thank you for your question. Yes, I'm going to add the Yocto support for the example. |
Thank you for your response. Looking forward to it. In meanwhile, I am trying to create a recipe for your repo on my own. I am using dunfell version of Yocto. `| tmp/work/aarch64-mx8mn-fslc-linux/flutter-embedded-linux/1.0-r0/git/src/flutter/shell/platform/linux_embedded/surface/context_egl.h:92:26: error: no matching function for call to 'eglCreateWindowSurface' |tmp/work/aarch64-mx8mn-fslc-linux/flutter-embedded-linux/1.0-r0/git/src/flutter/shell/platform/linux_embedded/surface/linuxes_surface_gl_drm.h:48:36: note: in instantiation of member function 'flutter::ContextEgl<gbm_device, gbm_surface, gbm_surface>::CreateOffscreenSurface' requested here | tmp/work/aarch64-mx8mn-fslc-linux/flutter-embedded-linux/1.0-r0/recipe-sysroot/usr/include/EGL/egl.h:155:31: note: candidate function not viable: cannot convert argument of incomplete type 'gbm_surface *' to 'EGLNativeWindowType' (aka 'wl_egl_window *') for 3rd argument In my opinion, your EGL/egl.h and EGL/egl.h library which Yocto fetches from source (https://archive.mesa3d.org/; version 20.0.2) are different. |
@jmarijan
See: https://www.khronos.org/registry/EGL/api/EGL/eglplatform.h
|
@HidenoriMatsubayashi |
https://github.com/jwinarske/meta-flutter/blob/dunfell/recipes-graphics/flutter-embedded-linux/flutter-embedded-linux_git.bb @HidenoriMatsubayashi I understand you were asking around Toyota. I own the Toyota Flutter Embedder. |
@jwinarske Yes, I talked a little with Toyota's members a few weeks ago. Are you one of them? Toyota's Flutter Embedder is focusing AGL, right? I'm interested in Flutter use in AGL and Toyota. Do you have any plans to open source? Especially, I'm interested in what to do with plugins such as video player and webview. |
Open source plans are out of my hands. If/when it does, it will happen through AGL (Yocto based). The flutter-engine recipe won' change much beyond this one, if at all. As far as plugins go I prefer manually loading a shared module, oppose to statically linking the plugin code. If the plugin is in the filesystem, then it gets loaded, otherwise returns not implemented on the channel. It keeps a clean demarcation between random plugin authors and application owners. So having a plugin that can be built for GTK Linux or standalone plugin (shared module with known API including version) would meet the requirement. Otherwise trying to cross compile a plugin using Flutter tools would require binary repository package changes not standard between organizations. So alignment on plugins is a need. |
I see. Thank you for sharing! |
Updated recipes here. Each example app is a separate recipe. Patches are specific to dunfell (libweston-8). I renamed the bins so they can be installed at the same time. There is currently an issue with XDG protocol hanging. Seems you're missing a surface commit, which also indicates you're building with older Wayland Protocol and Weston. |
Could you give me some more information? Do you mean that |
I get the following error: From f7f5e4e69adae518824dfcfe1002129d2cb19f3a Mon Sep 17 00:00:00 2001 cmake/build.cmake | 2 +- diff --git a/cmake/build.cmake b/cmake/build.cmake
Once the configure phase passes, there are many compilation errors. It's like clang doesn't find all the required include files. |
@TomohideMorimoto Please check your build environment and fix properly. |
I managed to build flutter-wayland-client under Yocto. Here what I have changed:
|
I would like to confirm. wayland-protocol isn't explicitly added, but It exists in meta/recipes-graphics/wayland. So, I think it's okay without it. Are you cross-building using the SDK/toolchain generated by Yocto? |
A meta-layer is always in a separate source repo, otherwise you clone the same repo twice, and you end up with source in your meta layer. Not a good pattern. Why not just reference my layer? Not to mention it's going to get some updates. |
Thank you for your advice. I'm wondering if we should make a new repo for the yocto recipe. By the way, just wondering, is your activity on here in a position as Toyota or personal? |
Personal. |
Following the commit ae9e975, the above patch I posted to cross-compile in Yocto is no longer required. |
Do you have a plan to add a Yocto support for flutter-embedded-linux?
Yocto Layer for the Flutter already exists :
https://github.com/jwinarske/meta-flutter
It has support for some of the engines, such as flutter-pi.
The text was updated successfully, but these errors were encountered: