Travis is adding support for Windows (via Git Bash)

[samsieber]

https://blog.travis-ci.com/2018-10-11-windows-early-release

In theory, this would allow us to use only travis and drop appveyor completely. I think that'd be great to only have to use one service. Thoughts? If I spent more time getting familiar with the repo I might be able to implement this myself as a pull request... I'm not very confident in this area.

[gnzlbg]

I quickly got this working for the i686-pc-windows-msvc, x86_64-pc-windows-msvc and x86_64-pc-windows-gnu targets, but I am unable to get this working for i686-pc-windows-gnu (a toolchain with mingw32-darw has to be picked up but the incorrect one is found). Help would be appreciated.

[Larusso]

@gnzlbg mind showing how you started getting it to work?

[gnzlbg]

https://github.com/rust-lang-nursery/stdsimd/blob/master/.travis.yml#L71 Nothing fancy, just added the targets, and everything worked. The only target that did not work out-of-the box is i686-pc-windows-gnu.

[Larusso]

Cool thanks. I also just added the targets but it didn't work out of the box for me ;) I don't need a full windows coverage as of now so this might get me started. AppVeyor is so terribly slow ...

[gnzlbg]

You can drop a link to the branch where you tried, and I (or others) might be able to check it out later and see if we can help!

[Larusso]

I based my setup on the trust template. I only went through the files and commented out what I didn't want to test on ;) I think the main issue ist the missing support for native windows in all the scripts provided. It only checks for linux or osx. Let me play around a little bit more.

[lovasoa]

Did someone finally get something working ?

[Larusso]

I switched to travis windows a week ago. But I only managed to build the msvc targets. I also had to fall back to the native cargo. See the PR in my project: https://github.com/Larusso/unity-version-manager/pull/16/files