-
Notifications
You must be signed in to change notification settings - Fork 1.5k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Showing
7 changed files
with
33 additions
and
28 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
ae86536
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It seems this broke Appveyor.
ae86536
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Possible. I did not receive any alert. But I do not know how to fix this (and honestly, I do not care. I think, it creates more problems than it solves to have hundreds of CI configurations). However, if you know how to fix this, feel free to fix it.
ae86536
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes. Windows SDK Version 10.0 is not yet available in AppVeyor. Maybe it can be enabled somehow?
@danmar should we revert this commit and try to get it working in a PR? I am also not sure if it is a good idea to update to VS 2019 yet since it is very new. Personally I would stay with VS 2017 for a while. But I have not tried 2019 yet, maybe it is very stable already.
Edit:
The list at https://www.appveyor.com/docs/windows-images-software/ is not up to date. Visual Studio 2019 is already supported, and maybe more Windows SDK 10 versions than listed there also. So it should be possible to get AppVeyor working for VS 2019.
ae86536
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Feel free to revert it if you consider CI more important than having windows releases.
ae86536
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sorry if you maybe feel offended, that was not my intention. Personally I think CI is a great thing and we should try to get AppVeyor working. I would have no problem if it only does builds with VS 2019. I can fully understand that maintaining compatibility with older Visual Studios is too time consuming. I am not sure who set up the AppVeyor builds exactly and if it is somewhat important to support older Visual Studio releases. @danmar What do you think?
ae86536
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We should not revert this. Your task to build the windows releases is complex enough.
Imho the VS2013 builds are most important. If we have to disable the latest build in CI until appveyor supports it.. I do not like that at all but we can do it :-(.
But well I want to see if it can be solved first.
ae86536
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What is your opinion about using cmake in the appveyor builds? Appveyor does not have VS2019 yet anyway as far as I see so you have to run testrunner yourself if you switch to VS2019.
ae86536
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
According to appveyor/ci#2907 (comment) Visual Studio 2019 should be available.
ae86536
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ok
ae86536
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I made a quick hack with 8a63a5d to make appveyor happy again. Can somebody please try to fix this problem better?