-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Hard dependency of TLS implementation makes SQLx unbuildable on some platforms #1750
Comments
We are working to make the runtime and TLS features orthogonal so you can disable TLS if you don't need it. That work isn't on the |
Not being able to disable tls is my only regret, hopefully this will be fixed soon. |
This would be wonderful for dockerized apps, and for sqlite apps. |
Yes, I'm working with sqlite and do not need tls feature enabled. Please add the seperated feature flags back, thx. |
I can't build for |
Rustls uses ring, which does not declare an SPDX license. Because of that, cargo deny signals this license as incompatible. The correct change would be to completely disable TLS since it is neither used nor needed, however `sqlx` does not currently support that. launchbadge/sqlx#914 launchbadge/sqlx#1750
Building for the WASI target is also interesting for us. Anything the community (happy to contribute!) can do to help move this along? |
It's been possible to build SQLx without a TLS backend since 0.7.0. Just use |
I know this is an duplicate of #914, but it seems that you guys are not aware that having to build
rustls
can be such a headache, in the meantime, development on thenext
branch seems have stalled.I am trying to build a project that is intended to be used in an embedded MIPS platform, on which
ring
(one ofrustls
's core dependencies, a crypto library) does not build (briansmith/ring#562).Making matters worse, the target device is extremely space constrained and we do not want to include OpenSSL because it simply does not fit. The target device only uses SQLite and does not connect to the Internet, including any TLS implementation would be a waste of space and memory.
The text was updated successfully, but these errors were encountered: