Please check the build logs for more information.
See Builds for ideas on how to fix a failed build, or Metadata for how to configure docs.rs builds.
If you believe this is docs.rs' fault, open an issue.
This project is an attempt at extracting the
compiletest utility from the Rust
compiletest utility is useful for library and plugin developers, who want
to include test programs that should fail to compile, issue warnings or
otherwise produce compile-time output.
To use in your project
compiletest-rs in your application, add the following to
[dev-dependencies] compiletest_rs = "*"
tests folder in the root folder of your project. Create a test file
with something like the following:
extern crate compiletest_rs as compiletest; use PathBuf;
Each mode corresponds to a folder with the same name in the
tests folder. That
is for the
compile-fail mode the test runner looks for the
Adding flags to the Rust compiler is a matter of assigning the correct field in the config.
config.target_rustcflags = Some;
This is useful (and necessary) for library development. Note that other secondary library dependencies may have their build artifacts placed in different (non-obvious) locations and these locations must also be added.
test-project folder for a complete working example using the
compiletest-rs utility. Simply
cd test-project and
cargo test to see the
run-passmode is strictly not necessary since it's baked right into Cargo, but I haven't bothered to take it out
- Find out if it is possible to capture the build flags during
compilation. Then it should be possible to for
compiletest-rsto capture (among other things) build dependencies (like
-L). In the case a library would depend on a second library, the generated
.rlibfor the second library may end up in non-obvious places (and missing from the build path). Currently the work-around is to explicitly list the search paths as extra rustc flags.