mirror of
https://github.com/mozilla/gecko-dev.git
synced 2024-10-08 19:04:45 +00:00
1c2fbc9d73
Update:
- Glean to v53.1.0
- UniFFI to v0.24.1
- application-services to a recent nightly that uses the above
versions
- Updated `rusqlite` in toolkit/library/rust/shared/Cargo.toml
- Updated `uniffi-bindgen-gecko-js` to work with the new UniFFI. Also
updated it's askama version.
- Vetted new cargo dependencies
Ran `mach uniffi generate` to regenerate the code.
Differential Revision: https://phabricator.services.mozilla.com/D181872
|
||
|---|---|---|
| .. | ||
| src | ||
| .cargo-checksum.json | ||
| Cargo.toml | ||
| README.md | ||
This crate contains helper code for testing bindings. Our general system is to generate bindings for the libraries from the examples and fixtures directories, then execute a script that tests the bindings.
Each bindings crate can do this in a different way, but the typical system is:
- Construct a
UniFFITestHelperstruct to assist the process - Call
UniFFITestHelper.create_out_dir()to create a temp directory to store testing files - Call
UniFFITestHelper.copy_cdylibs_to_out_dir()to copy the dylib artifacts for the example/fixture library to theout_dir. This is needed because the bindings code dynamically links to or loads from this library. - Call
UniFFITestHelper.get_compile_sources()to iterate over (udl_path,uniffi_config_path) pairs and generate the bindings from them. This step is specific to the bindings language, it may mean creating a .jar file, compiling a binary, or just copying script files over. - Execute the test script and check if it succeeds. This step is also specific to the bindings language.