tokio-xmpp: Fix build on insecure-tcp
insecure-tcp requires the io-util feature of tokio, so let’s enable it
there.
Fixes this error:
5 | use tokio::{io::BufStream, net::TcpStream};
| ^^^^^^^^^^^^^ no `BufStream` in `io`
This commit is contained in:
parent
4148e9d165
commit
b8f64037a9
2 changed files with 2 additions and 1 deletions
|
|
@ -52,7 +52,7 @@ tls-rust-webpki-roots = ["tls-rust", "webpki-roots"]
|
|||
tls-native = ["tokio-native-tls", "native-tls"]
|
||||
starttls-native = ["starttls", "tls-native"]
|
||||
starttls-rust = ["starttls", "tls-rust"]
|
||||
insecure-tcp = []
|
||||
insecure-tcp = ["tokio/io-util"]
|
||||
syntax-highlighting = ["syntect"]
|
||||
# Enable serde support in jid crate
|
||||
serde = [ "xmpp-parsers/serde" ]
|
||||
|
|
|
|||
|
|
@ -33,6 +33,7 @@ XXXX-YY-ZZ RELEASER <admin@example.com>
|
|||
actual encryption and decryption to the kernel, which in turn can
|
||||
delegate it to a hardware implementations if available. This depends
|
||||
on the `tls-rust-ktls` feature. (!458, !490)
|
||||
- Building with insecure-tcp and no other feature got fixed.
|
||||
|
||||
Version 4.0.0:
|
||||
2024-07-26 Maxime “pep” Buquet <pep@bouah.net>
|
||||
|
|
|
|||
Loading…
Reference in a new issue