Expose BinaryMessenger from FlutterEngine in Windows API #62871
Assignees
Labels
a: desktop
Running on desktop
engine
flutter/engine repository. See also e: labels.
P2
Important issues not at the top of the work list
Milestone
Comments
stuartmorgan-g
added
a: desktop
12 tasks
stuartmorgan-g
added a commit
to flutter/engine
that referenced
this issue
Aug 16, 2020
Makes BinaryMessenger available from FlutterEngine, rather than just the plugin registrar. This allows for method channels directly in applications without building them as plugins, and matches the other platforms. Requires some restructuring of code and GN targets in the client wrappers to make the internals in the shared section usable by the implementations of platform-specific parts of the wrappers. Also fixes a latent issue with EnableInputBlocking symbols being declared but not defined for Windows that came up during testing of the restructuring. Fixes flutter/flutter#62871
stuartmorgan-g
added a commit
to flutter/engine
that referenced
this issue
Aug 17, 2020
Relands #20399 Makes BinaryMessenger available from FlutterEngine, rather than just the plugin registrar. This allows for method channels directly in applications without building them as plugins, and matches the other platforms. Requires some restructuring of code and GN targets in the client wrappers to make the internals in the shared section usable by the implementations of platform-specific parts of the wrappers. Also fixes a latent issue with EnableInputBlocking symbols being declared but not defined for Windows that came up during testing of the restructing. Fixes flutter/flutter#62871
|
This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Currently the only way to get a
BinaryMessengeris as a plugin. Adding an engine->messenger getter to the C API is simple, but the C++ wrapper will need to be extracted fromplugin_registrar.ccso that it can be re-used.The text was updated successfully, but these errors were encountered: