I'm actually trying to debug a rust issue right now and have some questions. I've done the |mach vendor rust| step and got all the vendored crates. Now let's say that in one of the dependencies (the 'cmake' crate in my case) there's some sort of behaviour that I'd like to investigate/debug. If I edit the third_party/rust/cmake/src/lib.rs in-place, the build fails because of a hash mismatch. The error suggests forking the repo and using [replace] instead - so I tried do that by copying the cmake folder to third_party/rust/cmake-fork and putting a [replace] section in toolkit/library/rust/Cargo.toml to point to it. However if I do that the force-cargo-build step in the build fails saying the lock file needs updating but --locked was passed.
Am I on the right track here, or is there some other easier way to modify one of the vendored crates for local debugging? On Wed, Nov 9, 2016 at 6:20 AM, Ted Mielczarek <t...@mielczarek.org> wrote: > I recently wrote some documentation on how to add Rust code to Gecko: > http://gecko.readthedocs.io/en/latest/build/buildsystem/rust.html > > It should be fairly straightforward for most use cases (thanks to Nathan > Froyd for doing the lion's share of the work to make it so), but if > there's anything that's unclear feel free to ask for clarification. > > -Ted > _______________________________________________ > dev-platform mailing list > dev-platform@lists.mozilla.org > https://lists.mozilla.org/listinfo/dev-platform _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
