\n
A couple of weeks ago I gave a talk titled \u201cLeveraging Rust to build cross-platform mobile libraries\u201d<\/a>. You can find my slides as a PDF<\/a>. It was part of the Rusty Days<\/a> Webference, an online conference that was initially planned to happen in Poland, but had to move online. Definitely check out the other talks<\/a>.<\/p>\n One thing I wanted to achieve with that talk is putting that knowledge out there. While multiple teams at Mozilla are already building cross-platform libraries, with a focus on mobile integration, the available material and documentation is lacking. I\u2019d like to see better guides online, and I probably have to start with what we have done. But that should also be encouragement for those out there doing similar things to blog, tweet & speak about it.<\/p>\n I\u2019d like to hear about it. Find me on Twitter (@badboy_<\/a>) or drop me an email<\/a>.<\/p>\n I won\u2019t reiterate the full talk (go watch it<\/a>, really!), so this is just a brief overview of the Glean SDK itself.<\/p>\n The Glean SDK is our approach to build a modern Telemetry library, used in Mozilla\u2019s mobile products and soon in Firefox on Desktop as well.<\/p>\n The SDK consists of multiple components, spanning multiple programming languages for different implementations. All of the Glean SDK lives in the GitHub repository at mozilla\/glean<\/a>. This is a rough diagram of the Glean SDK tech stack:<\/p>\n On the very bottom we have On top of that sits The top layer of the Glean SDK are the different language implementations<\/a>. Language implementations expose a nice ergonomic API to initialize Glean and record metrics in the respective language. Additionally each implementation handles some special cases for the platform they are running on, like gathering application and platform data or hooking into system events. The nice API calls into the Glean SDK using the exposed FFI functions of (\u201cThis Week in Glean\u201d is a series of blog posts that the Glean Team at Mozilla is using to try to communicate better about our work. They could be release … Read more<\/a><\/p>\n","protected":false},"author":1756,"featured_media":197,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[448297],"tags":[],"coauthors":[],"_links":{"self":[{"href":"https:\/\/blog.mozilla.org\/data\/wp-json\/wp\/v2\/posts\/232"}],"collection":[{"href":"https:\/\/blog.mozilla.org\/data\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/blog.mozilla.org\/data\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/blog.mozilla.org\/data\/wp-json\/wp\/v2\/users\/1756"}],"replies":[{"embeddable":true,"href":"https:\/\/blog.mozilla.org\/data\/wp-json\/wp\/v2\/comments?post=232"}],"version-history":[{"count":0,"href":"https:\/\/blog.mozilla.org\/data\/wp-json\/wp\/v2\/posts\/232\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/blog.mozilla.org\/data\/wp-json\/wp\/v2\/media\/197"}],"wp:attachment":[{"href":"https:\/\/blog.mozilla.org\/data\/wp-json\/wp\/v2\/media?parent=232"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blog.mozilla.org\/data\/wp-json\/wp\/v2\/categories?post=232"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blog.mozilla.org\/data\/wp-json\/wp\/v2\/tags?post=232"},{"taxonomy":"author","embeddable":true,"href":"https:\/\/blog.mozilla.org\/data\/wp-json\/wp\/v2\/coauthors?post=232"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}Who else is using Rust to build cross-platform libraries, targetting mobile?<\/h2>\n
The Glean SDK<\/h2>\n
![\"Glean](\"http:\/\/blog.mozilla.org\/data\/files\/2020\/09\/glean-stack.png\")
<\/p>\nglean-core<\/code>, a pure Rust library that is the heart of the SDK. It\u2019s responsible for controlling the database, storing data and handling additional logic (e.g.\u00a0assembling pings, clearing data, ..). As it is pure Rust we can rely on all Rust tooling for its development. We can write tests that cargo test<\/code> picks up. We can generate the full API documentation thanks to rustdoc<\/code> and we rely on clippy<\/code> to tell us when our code is suboptimal. Working on glean-core<\/code> should be possible for everyone that knows some Rust.<\/p>\nglean-ffi<\/code>. This is the FFI layer connecting glean-core<\/code> with everything else. While glean-core is pure Rust, it doesn\u2019t actually provide the nice API<\/em> we intend for users of Glean. That one is later implemented on top of it all. glean-ffi doesn\u2019t contain much logic. It\u2019s a translation between the proper Rust API of glean-core and C-compatible functions exposed into the dynamic library. In it we rely on the excellent ffi-support<\/code> crate<\/a>. ffi-support knows how to translate between Rust and C types, offers a nice (and safer) abstraction for C strings. glean-ffi holds some<\/em> state: the instantiated global Glean object and metric objects. We don\u2019t need to pass pointers back and forth. Instead we use opaque handles that index into a map held inside the FFI crate.<\/p>\nglean-ffi<\/code>. Unfortunately at the moment different language implementations carry different amounts of actual logic in them. Sometimes metric implementations require this (e.g.\u00a0we rely on the clock source of Kotlin for timing metrics), in other parts we just didn\u2019t move the logic out of the implementations yet. We\u2019re actively working on moving logic into the Rust part where we can<\/a> and might eventually use some code generation to unify the other parts. uniffi<\/a> is a current experiment for a multi-language bindings generator for Rust we might end up using.<\/p>\n","protected":false},"excerpt":{"rendered":"