| commit | c25cf09d6dd891ad80f9434d5d800cc1049ef8bf | [log] [tgz] |
|---|---|---|
| author | Hannes Winkler <hanneswinkler2000@web.de> | Thu Aug 08 21:11:22 2024 +0200 |
| committer | GitHub <noreply@github.com> | Thu Aug 08 19:11:22 2024 +0000 |
| tree | bb86d5219450afc8e9206b91c2ed3b07017cdd8b | |
| parent | 597082d9d85b183f3c57cc79e40cb8f045f0a99a [diff] |
Add EGL Surface backing store (#43683) Allows using an EGL surface as a flutter backing store. Way more convenient for GBM than hacking gbm bo's into GL FBOs. This resolves https://github.com/flutter/flutter/issues/58363 Currently, the embedder API assumes that the compositor (if it exists) will let flutter render into FBOs or Textures and then composite the whole thing onto the actual (EGL) window surface. I think this assumption is also documented a bit in https://github.com/flutter/flutter/issues/38466 However, in my case, I want let the hardware do the composition (using the linux KMS API), and render each flutter layer into it's own EGL surface. It's possible to hack around this by creating your own GBM BOs, importing those as EGL images, then importing those as GL Render Buffers and attaching those to GL FBOs and that works (tested it). However, that's basically reimplementing 50% of the whole GBM/EGL "window" system integration for no reason. This PR adds: 1. To the embedder API: - a new kind of OpenGL Backing store: `FlutterOpenGLSurface` - consisting of just a `make_current` and destruction callback (plus userdata) - the make_current callback should make the target surface current, i.e. `eglMakeCurrent(..., surf, surf)` - will be called by the engine before rendering onto the backing store 2. Some wiring to call make_current before rendering into the backing store ## TODO: [C++, Objective-C, Java style guides]: https://github.com/flutter/engine/blob/main/CONTRIBUTING.md#style
Flutter is Google's SDK for crafting beautiful, fast user experiences for mobile, web, and desktop from a single codebase. Flutter works with existing code, is used by developers and organizations around the world, and is free and open source.
The Flutter Engine is a portable runtime for hosting Flutter applications. It implements Flutter's core libraries, including animation and graphics, file and network I/O, accessibility support, plugin architecture, and a Dart runtime and compile toolchain. Most developers will interact with Flutter via the Flutter Framework, which provides a modern, reactive framework, and a rich set of platform, layout and foundation widgets.
If you want to run/contribute to Flutter Web engine, more tooling can be found at felt. This is a tool written to make web engine development experience easy.
If you are new to Flutter, then you will find more general information on the Flutter project, including tutorials and samples, on our Web site at Flutter.dev. For specific information about Flutter's APIs, consider our API reference which can be found at the docs.flutter.dev.
Flutter is a fully open source project, and we welcome contributions. Information on how to get started can be found at our contributor guide.