Unfortunately Cargo doesn't actually parse these! Cargo should probably
print a warning saying they're not used...

This is really annoying, since we can't use cfg(test) for doctests.

Until https://github.com/rust-lang/rust/issues/52652 is fixed,
unwinding on panic is potentially unsound in a mixed C/Rust codebase.

The codebase is supposed to be panic-free already, but just to be safe.

This started mattering at commit d1820c15.

Fixes #27199; bugfix on tor-0.3.3.1-alpha.

Due to linker issues (#25386) when testing Rust code which calls C,
all tests which touch FFI code should now be feature-gated behind the
"test-c-from-rust" flag.  To run this test code, cargo must be called
with `cargo test --features="test-c-from-rust"`.

 * FIXES #26398: https://bugs.torproject.org/26398

 * FIXES #24659: https://bugs.torproject.org/24659

 * FIXES #24660: https://bugs.torproject.org/24660

Allows an optional no-op for testing purposes

Sebastian Hahn authored 7 years ago and Nick Mathewson committed 7 years ago

This adds a couple of configure commands to control whether we're
requiring all dependencies to be available locally (default) or not
(--enable-cargo-online-mode). When building from a tarball, we require
the RUST_DEPENDENCIES variable to point to the local repository of
crates. This also adds src/ext/rust as a git submodule that contains
such a local repository for easy setup.

Sebastian Hahn authored 7 years ago and Nick Mathewson committed 7 years ago

This gives an indication in the log that Tor was built with Rust
support, as well as laying some groundwork for further string-returning
APIs to be converted to Rust