It should be possible to build gtk applications written in rust for the new android backend, given that the rust bindings do not use introspection at build time (sources are pregenerated).
As far as I see, there are two issues that are currently preventing this:
- For android, we want a "single-pass" ninja invocation to build the whole source+dependency tree, which as far as I understand isn't possible with rust, as it wants to use pkg-config to resolve the dependencies.
- The glue code wants to call
main(int argc, char **argv, char **envp), as I doubt that rustc will expose such an entry symbol by itself, there is likely need for more glue.
My potential idea was to build the rust application as static library, as to avoid rustc doing any symbol resolving. Instead meson should take the produced static library and link it with its dependencies built from the subprojects (this has the added benefit of meson also automatically linking the glue in correctly).
It should be possible to build gtk applications written in rust for the new android backend, given that the rust bindings do not use introspection at build time (sources are pregenerated).
As far as I see, there are two issues that are currently preventing this:
main(int argc, char **argv, char **envp), as I doubt that rustc will expose such an entry symbol by itself, there is likely need for more glue.My potential idea was to build the rust application as static library, as to avoid rustc doing any symbol resolving. Instead meson should take the produced static library and link it with its dependencies built from the subprojects (this has the added benefit of meson also automatically linking the glue in correctly).