Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Why using rustls instead of native-tls? #2

Closed
asv7c2 opened this issue Dec 21, 2018 · 2 comments
Closed

Why using rustls instead of native-tls? #2

asv7c2 opened this issue Dec 21, 2018 · 2 comments
Labels
question Further information is requested

Comments

@asv7c2
Copy link

asv7c2 commented Dec 21, 2018

Because adding rustls requires gcc toolchain (on windows) and perl for building ring (rustls dependency).

@lolgesten lolgesten added the question Further information is requested label Jan 29, 2019
@lolgesten
Copy link
Contributor

@Asv1 I like the idea of a "pure rust" TLS. That might not be the perfect choice.

@asv7c2 asv7c2 closed this as completed Jan 31, 2019
@polarathene
Copy link

polarathene commented Dec 4, 2019

Is this why I had a failure trying to build for Windows?(ureq worked fine on my linux system, only changed the build target):

cargo build --target=i686-pc-windows-msvc
   Compiling winapi v0.3.8
   Compiling serde v1.0.103
   Compiling ring v0.16.9
   Compiling idna v0.1.5
   Compiling idna v0.2.0
error: failed to run custom build command for `ring v0.16.9`

Caused by:
  process didn't exit successfully: `/projects/my_project/target/debug/build/ring-00f0df746747f3f2/build-script-build` (exit code: 101)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

3 participants