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

To those wanting to use HTTP and/or HTTPS #205

Open
LexiBigCheese opened this issue Jan 19, 2025 · 0 comments
Open

To those wanting to use HTTP and/or HTTPS #205

LexiBigCheese opened this issue Jan 19, 2025 · 0 comments

Comments

@LexiBigCheese
Copy link

LexiBigCheese commented Jan 19, 2025

You'll want to comment out the assertion that causes issue #174 to have a panic, then cargo clean so cargo rebuilds std with this change.
Then, patch the ring crate to be the one I'm trying to get pulled into the main branch,
EDIT: It has been pulled!
EDIT2: Note: Point at ring's main branch.

[patch.crates-io]
ring = {git = "https://github.com/briansmith/ring"}

and ensure

[profile.dev.package.ring]
opt-level = 1
[profile.release.package.ring]
opt-level = 1

Note that patch and profile sections go in Cargo.toml, if you're using a cargo workspace, it does in the workspace's Cargo.toml
Additionally, you'll want the environment variable

export CFLAGS_armv6k_nintendo_3ds="-march=armv6k -mfloat-abi=hard -finline-limit=100000"

And now, the minreq crate will now let you do https.
Having a timeout may be that which causes the ureq crate to fail, I've been told to look into yielding when listening on an mpsc::Receiver, but I'm not that great at modifying std, so instead I just modified and patched ehttp to use minreq on cfg(target_os = "horizon")

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

No branches or pull requests

1 participant