mirror of
https://github.com/facebook/sapling.git
synced 2024-10-07 07:17:55 +03:00
b4f725330e
Summary: When using our vendored set of crates, cmake doesn't have any dependency information to use to invalidate the Cargo.lock file when we update crate versions. In addition, since we're vendoring from a local directory, cargo itself doesn't seem to want to re-assess the dependencies in that same situation, leading to confusing error messages like this when we want to build rust targets: ``` error: failed to select a version for the requirement `anyhow = "= 1.0.26"` candidate versions found which didn't match: 1.0.28 ``` This commit addresses this issue by removing the `Cargo.lock` that may be alongside the `Cargo.toml` prior to invoking `cargo`. `cargo` is pretty quick at recomputing the deps so this has neglible overhead. Reviewed By: xavierd Differential Revision: D21394363 fbshipit-source-id: 547db2e2395a47aed77d9597e659eb2d96e274dd |
||
|---|---|---|
| .. | ||
| CompilerSettingsUnix.cmake | ||
| eden-config.cpp.in | ||
| eden-config.h.in | ||
| eden-config.py.in | ||
| EdenConfigChecks.cmake | ||
| FindLibGit2.cmake | ||
| FindLZ4.cmake | ||
| FindPrjfs.cmake | ||
| FindSELinux.cmake | ||
| FindSqlite3.cmake | ||
| RustStaticLibrary.cmake | ||