2020-11-03 00:03:00 +01:00
|
|
|
This folder integrates Rust crates.io fetching into Bazel.
|
|
|
|
|
|
2020-12-18 02:56:56 +01:00
|
|
|
To update dependencies, ensure a local Rust environment is available
|
|
|
|
|
(eg install rustup), then run:
|
|
|
|
|
|
|
|
|
|
```
|
|
|
|
|
cargo install cargo-raze --version 0.8.0
|
|
|
|
|
```
|
|
|
|
|
|
2020-11-03 00:03:00 +01:00
|
|
|
After updating dependencies in ../rslib/Cargo.toml, change to this
|
|
|
|
|
folder and run python update.py to update the external Bazel repositories
|
|
|
|
|
to point to the updated deps.
|
|
|
|
|
|
|
|
|
|
A couple of crates need extra work to build with Bazel, and are listed
|
2020-11-24 09:41:03 +01:00
|
|
|
in ../Cargo.toml. For example:
|
2020-11-03 00:03:00 +01:00
|
|
|
|
|
|
|
|
```toml
|
2020-11-24 09:41:03 +01:00
|
|
|
[package.metadata.raze.crates.pyo3.'*']
|
2020-12-15 11:28:10 +01:00
|
|
|
compile_data_attr = "glob([\"**\"])"
|
2020-11-03 00:03:00 +01:00
|
|
|
```
|
|
|
|
|
|
2020-11-10 00:47:24 +01:00
|
|
|
With minor version updates, you should not normally need to modify
|
|
|
|
|
the entries in that file.
|
2021-03-15 04:29:36 +01:00
|
|
|
|
|
|
|
|
Because update.py modifies a lot of files in remote/, it makes it difficult to
|
|
|
|
|
review in a PR, and the changes can sometimes break platforms like Windows. For
|
|
|
|
|
this reason, please don't submit PRs that do minor version bumps - those will
|
|
|
|
|
typically be done after stable releases. If you need a new crate for a feature
|
|
|
|
|
you're working on, please raise it in an issue first.
|
