Fuchsia uses third-party Rust crates. They are placed in //third-party/rust_crates/vendor
. This set of crates is based on the dependencies listed in //third_party/rust_crates/Cargo.toml
. If you don't find a crate that you want to use, you may bring that into Fuchsia.
To add a third-party crate, the steps are:
Pay attention to transitive dependencies: A third-party crate may depend on other third-party crates. List all the new crates that end up with being brought in, in the OSRB review. For OSRB, follow the instructions under the “Process for 3rd Party Hosted Code” section in this document.
Note: You need to get OSRB approval first before uploading a CL for review.
Change directory to Fuchsia repo base directory (For example, cd ~/fuchsia
).
Add an entry in third_party/rust_crates/Cargo.toml
for the crate you want to add.
Run the following command to calculate the dependencies and download the crates:
fx update-rustc-third-party
This command downloads all crates listed in rust_crates/Cargo.toml
as well as their dependencies, places them in the vendor
directory, and updates Cargo.toml
and Cargo.lock
.
Note: on Linux, pkg-config
needs to be installed.
Do a build test. For example:
fx set core.x64 && fx build
Run the following command to update crate-map:
fx update-rustc-crate-map --output third_party/rust_crates/crate_map.json
This command updates crate_map.json
with information about the Rust crates available for each target (Fuchsia and host). Note that this step uses information from the build step - make sure that the build for the third_party
folder has succeeded first before running this command. This would be part of the fx build
you are expected to run in the previous step.
Identify all the crates to be brought (see the diff in //third_party/rust_crates/vendor/
). Do not submit the CL for code review. Get OSRB approval first. If there are any files in the source repository that are not included when vendored, make a note of that for the OSRB reviewer. For example, font files that are only used for testing but are excluded when the crate is vendored. If you are not a Google employee, you will need to ask a Google employee to do this part for you.
After the OSRB approval, upload the change for review to Gerrit.
Get code-review+2
and merge the change into third_party/rust_crates.
Updating is very similar to adding a crate.
To update a third-party crate, do the following:
third_party/rust_crates/Cargo.toml
and rerunning fx update-rustc-third-party
as above.//third_party/rust_crates/vendor/
). Again, do not submit the CL for code review until you've received OSRB approval for any new dependencies added.If the project requires importing a new third-party crate to handle functionality related to Unicode and internationalization, prefer crates from the UNIC project when available.
The following non-UNIC crates are already vendored and are grandfathered, but we will aim to migrate to UNIC equivalents when possible.
We should encourage upstream dependencies to migrate to UNIC as well.
UNIC crates have distinct advantages over other crates:
UNIC crates are developed in a single repo, with shared common code and a single version scheme.
UNIC crates are generated from a consistent set of Unicode data files.
The UNIC project is aiming for comprehensive feature coverage, to be like ICU for Rust. If the project succeeds, our dependencies on unrelated Unicode crates should be reduced over time.