Alekos Filini

> i've got this error when running `cargo check --target wasm32-unknown-unknown`: > > ``` > failed to resolve: use of undeclared type or module `futures_timer` > --> /Users/admin/.cargo/registry/src/github.com-1ecc6299db9ec823/async-std-1.6.2/src/utils.rs:84:29 > |...

It looks like libevent is building fine (albeit with a few warnings), but then tor doesn't like to link with it. I don't have an arm laptop, I'll see if...

I don't remember how to do this, but there should be a way to get the full log of all the checks run by `configure`. There should be at least...

No these are just warnings, they shouldn't make it all fail. There's a log somewhere that lists all the "checks" run by configure to figure out the right compiling flags....

@i5hi if you are targeting android I think your `CC` env variable was wrong, it was pointing to a non-android linux toolchain. Usually if you have the NDK in your...

That's interesting, let me know if you figure out why that's happening.

Not sure exactly what's best because I haven't compared many of them, but we've been using `ureq` with BDK since it's pretty lightweight and they seem to support socks5 proxies...

I usually cross-compile from linux, which as far as i know is also the recommended way for the tor daemon itself (not just this library). I can keep this issue...

I would try adding some code to enforce only one instance of Tor running at a time: unfortunately Tor internally uses a lot of `static` variables to store the current...

Try enabling the `vendored-openssl` feature which will compile and link to a static version of openssl