In #49 I tried to add AppVeyor (a CI for Windows) by copying the config used by regex. It didn't work for each target and I have no way to debug and fix this.
I'd be very happy if someone could have a look at this! :smiley:
I've been trying to install cargo-edit on my Windows computer, but to no avail. The problem is building the curl dependency. I've ran into the following two issues:
https://github.com/carllerche/curl-rust/issues/71
https://github.com/carllerche/curl-rust/issues/81
I tried to run it in mingw32, but that doesn't have make in it. Better Windows support would be nice.
I've switched over to using the MSVC ABI version of Rust, and cargo-edit installs just fine.
Oh, that's good. I do have the GNU ABI installed on this machine. Let me try on my laptop.
I just got the latest nightly MSVC Rust, and now cargo-edit isn't installing anymore...
Great that you keep trying, @Seeker14491 :)
Would moving from curl to hyper help in your opinion? I guess it'll still need to build openssl, though.
@killercup I think it would, since the problem is with building curl. I've never used curl or hyper though, so I'm not knowledgeable in this area.
problematic to build curl-sys here either
Could you try building the branch from
https://github.com/killercup/cargo-edit/pull/67 ? Thanks!
Heather [email protected] schrieb am Mo., 18. Jan. 2016 um 14:15:
problematic to build curl-sys here either
—
Reply to this email directly or view it on GitHub
https://github.com/killercup/cargo-edit/issues/55#issuecomment-172524280
.
I've done some testing on Rust 1.7 stable running on Windows Server 2012 R2. I tested both the MSVC and GNU ABI versions of Rust.
MSVC: Running cargo install cargo-edit works.
GNU: Running cargo install cargo-edit fails with a curl-sys error.
I'm unable to test the hyper branch, as when I clone it and run cargo install --path ., I get the message multiple packages with binaries found: cargo-edit, cargo-list-empty-test-fix
, cargo-list-test-fixture, cargo-rm-test-fixture. I'd like to know how to resolve this so I can test the hyper branch.
I used the command cargo build --release instead to build the hyper branch, and these are the results:
MSVC: Fails with openssl error.
GNU: Works
Thanks for the research! What would you suggest we do? Also, can you build
cargo itself with the GNU tool chain? If that works we can maybe copy what
they do.
Brian Bowman [email protected] schrieb am Sa., 5. März 2016 um
06:59:
I used the command cargo build --release instead to build the hyper
branch, and these are the results:_MSVC_: Fails with openssl error.
_GNU_: Works
—
Reply to this email directly or view it on GitHub
https://github.com/killercup/cargo-edit/issues/55#issuecomment-192584835
.
@killercup I've tried building cargo on the GNU toolchain, and it errors with the same curl-sys error.
I installed cargo-edit in my cygwin environment with the GNU toolchain. Building and installation worked out fine (after resolving curl-sys error), but executing cargo add something doesn't do anything (except for utilizing one core) and never returns. Can't figure out why. Any idea? Shall I open another issue for this problem?
Would hyper resolve this issue?
@sebasgarcep see https://github.com/killercup/cargo-edit/issues/55#issuecomment-192584835. This may be outdated, though, since most problem seem to stem from using OpenSSL. Looking at the dependencies for reqwest (a simple interface for hyper), it seems to depend on native-tls, which will use SChannel on Windows and Security.framework on macOS. As you can see, I've started porting this to hyper some time ago. I'm kind of weary switch to something new now (but I guess it would be reqwest), as I'm pretty sure, I'd end up rewriting the whole crate…
If you are interested: I'd make a crate to access crates.io data (with a futures-rs/tokio based interface ideally), switch to a style-preserving TOML writer (which AFAIKT does not exist yet), and switch to clap for CLI commands to get autocompletions for free. Oh, or I'd try to integrate add/rm into Cargo itself! :)
Add/rm should come with cargo by default. :)
On a sidenote I own a crate (still in it's infancy) to fetch from the crates.io API. I'd love to discuss its direction. https://github.com/sebasgarcep/crates-api
Interesting! Have you seen https://github.com/rust-lang/cargo/tree/master/src/crates-io?
In other news, I've created https://gitter.im/cargo-edit/Lobby if anyone wants to chat outside of Github issues. :)
Am 08.01.2017 um 03:35 schrieb Sebastian Garrido notifications@github.com:
Add/rm should come with cargo by default. :)
On a sidenote I own a crate (still in it's infancy) to fetch from the crates.io API. I'd love to discuss its direction. https://github.com/sebasgarcep/crates-api
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.
Hey everyone, I just tried to install cargo-edit on my Windows machine and ran into the same problem building curl-sys v0.1.35. I would really love to get it to work, it looks fantastic, exactly what I have been craving - but I am reluctant to switch to MSVC. What is the current status of this issue?
Most helpful comment
@sebasgarcep see https://github.com/killercup/cargo-edit/issues/55#issuecomment-192584835. This may be outdated, though, since most problem seem to stem from using OpenSSL. Looking at the dependencies for reqwest (a simple interface for hyper), it seems to depend on native-tls, which will use SChannel on Windows and Security.framework on macOS. As you can see, I've started porting this to hyper some time ago. I'm kind of weary switch to something new now (but I guess it would be reqwest), as I'm pretty sure, I'd end up rewriting the whole crate…
If you are interested: I'd make a crate to access crates.io data (with a futures-rs/tokio based interface ideally), switch to a style-preserving TOML writer (which AFAIKT does not exist yet), and switch to clap for CLI commands to get autocompletions for free. Oh, or I'd try to integrate add/rm into Cargo itself! :)