When following the instructions on README.md, specifically:
# Or any other static file server that supports the application/wasm mime type
cargo install https
I get a cargo error:
🦄 ~/ on 🌱 main[$!?]
❯ cargo install https
Updating crates.io index
Downloaded https v2.0.2
Downloaded 1 crate (4.5 KB) in 0.75s
Installing https v2.0.2
Updating crates.io index
Compiling https v2.0.2
error: failed to run custom build command for `https v2.0.2`
Caused by:
process didn't exit successfully: `/tmp/cargo-installWfK0Of/release/build/https-0a69f07ca86af835/build-script-build` (exit status: 1)
--- stderr
With http 2.0.0, http is no longer publishable on crates.io.
This is for a mundane reason of needing to vendor patched dependencies: https://github.com/thecoshman/http/pull/160#issuecomment-2143877822
Please install http from git by running
RUSTC_BOOTSTRAP=1 cargo install -f --git https://github.com/thecoshman/http
and then update as normal.
For use with cargo-update, also do
cargo install-update-config -e RUSTC_BOOTSTRAP=1 https
You will continue to only receive normal, full, releases.
error: failed to compile `https v2.0.2`, intermediate artifacts can be found at `/tmp/cargo-installWfK0Of`.
To reuse those artifacts with a future compilation, set the environment variable `CARGO_TARGET_DIR` to that path.
🦄 ~/ on 🌱 main[$!?]
❯ cargo --version
cargo 1.79.0 (ffa9cf99a 2024-06-03)
I know you mention in a comment above cargo install https that one could use any file server that supports the application/wasm mime type, but would be good to swap the instructions to something that currently works through cargo install.
When following the instructions on README.md, specifically:
I get a cargo error:
I know you mention in a comment above
cargo install https
that one could use any file server that supports the application/wasm mime type, but would be good to swap the instructions to something that currently works throughcargo install
.