| Age | Commit message (Collapse) | Author |
|---|
|
Closes #40469
Signed-off-by: David Goulet <dgoulet@torproject.org>
|
|
Only the final crate needs to be a `staticlib`, no need for all the
intermediate steps to produce staticlibs!
|
|
This is really annoying, since we can't use cfg(test) for doctests.
|
|
|
|
|
|
It was synonymous with the builtin "test" feature.
* FIXES #26399: https://bugs.torproject.org/26399
|
|
We need this trick because some of our Rust tests depend on our C
code, which in turn depend on other native libraries, which thereby
pulls a whole mess of our build system into "cargo test".
To solve this, we add a build script (build.rs) to set most of the
options that we want based on the contents of config.rust. Some
options can't be set, and need to go to the linker directly: we use
a linker replacement (link_rust.sh) for these. Both config.rust and
link_rust.sh are generated by autoconf for us.
This patch on its own should enough to make the crypto test build,
but not necessarily enough to make it pass.
|
|
This reverts commit 70d91bd059869a0ecf24ceb66942ada4f66f03c9.
|
|
This was already added to LIBTOR_A_SOURCES; it doesn't need to get
added again.
Fixes bug 26402. Bugfix on 0.3.4.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
|
|
Apparently rand and rand_core need to be built with the "std" feature
set consistently, or there will be a compile error in rngs/jitter.rs.
|
|
|
|
|
|
|
|
* FIXES #24659: https://bugs.torproject.org/24659
|
