I ran `./mach vendor rust` and `./mach cargo vet` and fixed the problems they
logged. Here's what I did (IIRC):
1. Updated the rev ID of all the `application-services` crates
2. Ran `./mach vendor rust` and `./mach cargo vet` and noted the errors
3. Removed `prost-derive` from the top-level `Cargo.toml` (`./mach vendor`
implied I should do this)
4. Removed the `policy.prost-derive` section from `supply-chain/config.toml`
(`./mach cargo vet` said I should do this)
5. `./mach cargo vet diff prost 0.11.9 0.12.1`
6. `./mach cargo vet certify`
7. `./mach cargo vet diff prost-derive 0.11.9 0.12.1`
8. `./mach cargo vet certify`
9. `./mach vendor rust`
Differential Revision: https://phabricator.services.mozilla.com/D191002
As of bug 1719535, libm is vendored, so we don't need to pull it out of
packed_simd anymore, and that was the last remaining difference between
upstream and our fork.
Differential Revision: https://phabricator.services.mozilla.com/D187413
This commit vendors the latest changes to the Suggest and Remote
Settings Rust components.
1. From the `application-services` source tree, I ran
`./tools/update-moz-central-vendoring.py ../m-c` to update the
revisions in the m-c source tree.
2. I added the Remote Settings component UDL file to
`toolkit/components/uniffi-bindgen-gecko-js/mach_commands.py`, and
updated `toolkit/components/uniffi-bindgen-gecko-js/config.toml` to
call the `RemoteSettings` constructor on the main thread. The
Suggest component uses the `RemoteSettingsConfig` type in its
public API, so we must generate bindings for the Remote Settings
component.
3. From the m-c source tree, I ran `./mach uniffi generate` to update
the generated UniFFI bindings.
Differential Revision: https://phabricator.services.mozilla.com/D187559
This is part 1 of 3 and vendors the [suggest component](https://github.com/mozilla/application-services/tree/main/components/suggest) from
application-services into m-c. `suggest` depends on `remote_settings`, so it was
also vendored. Part 2 will generate JS bindings with uniffi.
This is my first time doing this so I'll explain how I generated this patch in
case I did something wrong:
1. I manually added `suggest` to the following files:
* Top-level `Cargo.toml`
* `toolkit/library/rust/shared/Cargo.toml`
* `toolkit/library/rust/shared/lib.rs` -- I followed the example of `tabs`,
not sure if `suggest::uniffi_reexport_scaffolding!()` is necessary
2. I ran `./mach vendor rust`
That's it, there were no errors or problems.
Differential Revision: https://phabricator.services.mozilla.com/D187323
When using baked data provider in icu_capi, it uses icu_testdata crate.
But we add customized baked data as patched icu_testdata.
Depends on D167670
Differential Revision: https://phabricator.services.mozilla.com/D178156
When using baked data provider in icu_capi, it uses icu_testdata crate.
But we add customized baked data as patched icu_testdata.
Depends on D167670
Differential Revision: https://phabricator.services.mozilla.com/D178156
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
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
This adds a crate that override's the windows-targets crate to avoid
depending on the large import libraries in its dependencies.
Differential Revision: https://phabricator.services.mozilla.com/D183824
First, instead of using a path, use a version, which is more convenient
(via a patch in the top-level Cargo.toml).
Second, we make the build system itself enforce its presence for any
crate that is hooked to the build system as a program or library.
Finally, for each crate depending on the workspace hack, we add a
feature named after it, and make the build system enforce that the
feature is set. For now, this remains unused, but the end goal is to
have each of those features enable the dependencies each of these
crates need, so that if crate A and B need dependency D, but crate C
doesn't, building crate C doesn't build D.
Differential Revision: https://phabricator.services.mozilla.com/D180910
