Add appveyor.yml for appveyor.com Windows CI #31
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
As noted in the commit message of 167b085 , this PR is based on the knowledge and kind assistance of Michael Kriese alias @viceice in #29 and ppalaga#1
The present PR is not using Michael's PowerShell build scripts from #29 because they are not in master yet.
One of the project owners should activate AppVeyor CI for the current repository on https://www.appveyor.com/
I have activated AppVeyor for my fork and this is how the build output of 167b085 looks like: https://ci.appveyor.com/project/ppalaga/editorconfig-core-c/build/1.0.92
Note that
utf_8_char
test is failing, which is a known issue: https://ci.appveyor.com/project/ppalaga/editorconfig-core-c/build/1.0.92#L1049The main motivation for the present PR is to provide a canonical build for Windows including tests so that every future PR can be easily checked for eventual regressions. Having a Windows CI will also help to discuss and solve Windows related issues, like the already mentioned
utf_8_char
test failure.