rust-cargo

I want to create a Cargo.lock file in a Rust project from Cargo.toml based on what was available on 22 Feb 2017. I need to make version selection compatible to what would happen on that specific day. (No, don't have a version controlled Cargo.lock around somewhere.) I tried this to no avail: Clone the crates.io index into a local directory and check out an older commit that matches the desired date. Use the following lines in .cargo/config: [source.mycrates] registry = "file:///path/to/crates.io-index" # contains old checkout [source.crates-io] replace-with = "mycrates" Nevertheless, cargo

Let's assume I have a game with the following directory structure: /src /resources Cargo.toml I would like cargo build to copy the files in the resources directory and paste them in the same directory as the executable file. I know it is possible to do this using a custom build script, but this seems to be a common case that deserves special treatment. So the question is: does cargo provide a standard way of copying files to the target directory (using just Cargo.toml )? 来源： https://stackoverflow.com/questions/31080757/copy-files-to-the-target-directory-after-build

How can I get cargo to emit LLVM-IR instead of a binary for my project? I know that you can use the --emit=llvm-ir flag in rustc , but I've read some Github issues that show it's impossible to pass arbitrary compiler flags to cargo. Is there any way I can get cargo to emit LLVM-IR directly? Jacob There is cargo rustc to pass arbitrary compiler flags through Cargo to rustc . So I think: cargo rustc -- --emit=llvm-ir is what you want! EDIT: You should use Jacob's answer instead; a lot easier and less hacky. Build the project with cargo normally but add on the -v flag to show verbose output. The

A few days ago , cross-compiling to JavaScript via Emscripten has finally hit nightly. I wanted to compile a project using glium in that manner. However, there are still many Emscripten-related bugs in many crates. While maintainers usually fix those bugs quickly, they don't necessarily release those bug fixes to crates.io immediately. In my case, glium depends on glutin . glutin had a bug which is fixed now, but only in the git repository, not on crates.io . Note : glutin is not a direct dependency of my project; only an indirect one through glium ! How do I tell Cargo to use the glutin

I have a project that has a dependency (a cookie utility) that has a dependency on iron >= 0.3, <= 0.4 . My project has a dependency on iron 0.3 (so I can use the router middleware that hasn't yet been updated to the latest iron). When I try to compile my project, the cookie utility pulls the 0.4 version of iron, and I get errors since different versions of iron are being used. However, I can do: cargo update -p <cookie utility> which (usually) changes that package's dependency on iron to match the one I am using, and removes the extraneous dependency on iron 0.4 . (Bizarrely, I sometimes have

How can I force build.rs to run again without cleaning my whole project? I checked cargo build --help but I couldn't find anything related to build.rs . If you print "cargo:rerun-if-changed=<FILE>" the build will be triggered every time the file has changed. rerun-if-changed=PATH is a path to a file or directory which indicates that the build script should be re-run if it changes (detected by a more-recent last-modified timestamp on the file). Normally build scripts are re-run if any file inside the crate root changes, but this can be used to scope changes to just a small set of files. --

Is it acceptable to register generally useful (utilities / applications) on crates.io ? The FAQ doesn't address this and from browsing, there are examples of end-user applications (mostly command line tools). Or is crates.io? meant only for libraries? I'm asking this because the documentation hints at library use, semantic versioning for API's etc. but doesn't reference the case for packaging applications explicitly. Yes, because you can use cargo install to install and manage those applications system-wide. If this use were discouraged, I would suspect that command to not exist at all, or at