Add AppVeyor CI configuration

[rivy]

• includes testing to minimum working version (1.17.0)

[rivy]

@ogham , for this happen automatically, you'll need to set up an AppVeyor project which observes this repository (similar to Travis CI; see https://www.appveyor.com/docs).

A current completed test run is at https://ci.appveyor.com/project/rivy/rust-ansi-term/builds/23029890.

[retep998]

This appveyor.yml is overly complicated given this crate is pure Rust. Most of that environment setup stuff is totally extraneous and can be stripped out. For a simpler example see winapi's own appveyor.yml.

[rivy]

Well, @retep998 , I generally disagree.

Although it's not as simple as the winapi example, it was created for a broader use case and modeled after needs in "coreutils". Ultimately, this version is generally useful, documented, logs what it's doing and the environment that it is using, and has some workarounds for git/coverage and the gnu library problems mentioned in rust-lang/rust#47048 and rust-lang/rust#53454 (modeled after your suggestion). Yes, the gnu library workaround code is verbose, but, it's not certain when a dependent crate might bring in code that causes the library conflict.

Overall, I'm just offering a working starting point for the author to help advance the windows version of this story. It could obviously be tailored, and I'm open to suggested changes... or someone else could throw up a completely different working solution.

[retep998]

Why such an old Windows SDK?

[retep998]

If you ever wanted to support cross compilation from one arch to another, say to build for arm or aarch64, you would not be able to use the vcvars bat files as it would affect both build scripts compiled for the host architecture, and binaries compiled for the target architecture.

[retep998]

For crates that have C dependencies, yes getting MinGW setup correctly is important, and so your appveyor.yml is useful generally. However this crate only has winapi as a dependency, and so doesn't need any of the MinGW setup. Ultimately though, it's up to the crate author to decide what they want in terms of appveyor.

[retep998]

It seems wasteful to have installed a toolchain with rustup up above, only to then install a different toolchain entirely here.

[ogham]

Hey,

I signed up for AppVeyor. I'm still slowly learning how the Windows ecosystem works — as a crate maintainer I should really have more knowledge of it than I do right now. I'm going to merge this PR because I still want to have CI for Windows, and eventually I'd like to have learned the best way to do it myself.

Now to see if the build works...

Thanks 👍

[rivy]

I fixed a couple of things for this in PR #52, and I'm happy to help you set up a working automatic build/test system that includes windows.