Closed UNIDY2002 closed 1 year ago
Additional changes: set build image of AppVeyor CI to Visual Studio 2017
This is mainly because of some usages of c++17 features in Node 19 headers.
Since I have no access to the Travis CI logs, I am not sure whether the CI passes in Travis.
The Appveyor build passes. The Travis stack has not worked in years since they changed something with quotas and OS projects. Thank you, this looks excellent.
Additional changes: set build image of AppVeyor CI to Visual Studio 2017
This is mainly because of some usages of c++17 features in Node 19 headers.
Since I have no access to the Travis CI logs, I am not sure whether the CI passes in Travis.