example of running flutter application wayland #26
Comments
flutter_wayland was my initial wayland POC, and I haven't looked at it in quite some time. I'll make some updates and add example steps in the readme. |
I did look at the readme but it's not helpful:
and as readme suggest it does not work the follwing way:
so my question is how to bringup flutter using this layer at all ?! I must no use wayland. You wrote in previous issue that flutter-drm-eglstream-backend is working only for NVIDIA ( doesn't build anyway). I spent quite some times trying to figure out how it work but it's really very confusing. Thanks anyway |
Eglstream is for NVIDIA, drm-gbm is for Mesa. If you are not building an NVIDIA target image, you can't use it. You then use flutter-drm-gbm-backend. Standard embedded Linux graphics stuff. Yes without prior experience embedded Flutter has a steep learning curve, and can/will be frustrating. I know as I learned it from scratch without any help. |
Another bit of advice which will decrease frustration is to "bringup" the selected embedder on Linux desktop using an IDE such as CLion. This make understanding and resolving issues much faster. Once that all works, then move to the target. After that the only remaining items may be around install path and image symlink issues. |
My flutter_wayland repo has been updated. I am able to run the Gallery app on Fedora 24 with Keep in mind when switching channels or handling channel rolls (weekly) you need to clear things via:
Unless you're running pipeline builds that don't persist state. |
@jwinarske : ticket was closed too early :-) bitbake flutter-drm-gbm-backend is not building at all with FLUTTER_CHANNEL="master"
So in summary this layer seems to be working only for NVIDIA :-( |
built the with new flutter-wayland that was recently commited and used as suggested FLUTTER_CHANNEL="dev" I have the same error as before:
Note: I'm always building from scratch |
I closed it, as I addressed the filed issue. See the flutter_wayland repo for example. Stringing issues together doesn't help others. Given gallery currently builds with "dev", "master" is not something one normally targets unless you're generating PRs for the engine. "Beta" is recommended for flutter app development. At one point "master" was required for the gallery app, which is not always the case. The Sony recipes are currently autorev, as they are still in flux. If you want stability either find a commit you want to lock to and patch, try flutter-pi (drm-gbm), or write your own. All of the current public embedders are not a complete commercial solution. Mostly a best effort, or POC (flutter_wayland). I implemented/own the embedder Toyota is using, and it is far more sophisticated than any of these. This layer is a starting point for many. What SoC are you targeting? There are many companies using this layer including my own. |
I have built an image with the following setup added to my local.conf
How do I run the flutter-gallery App ? I couldn't find a lead
the follwoing isn't working:
The text was updated successfully, but these errors were encountered: