Jeffrey Walton
|
9cad63f5b4
|
Another AppVeyor attempt
Take 10 in this series
|
2017-08-03 23:26:32 -04:00 |
|
Jeffrey Walton
|
5ad6b2a7a6
|
Another AppVeyor attempt
Take 9 in this series
|
2017-08-03 21:25:12 -04:00 |
|
Jeffrey Walton
|
0622b2dc6b
|
ANother AppVeyor attempt
Take 2 in this series
|
2017-08-03 19:17:41 -04:00 |
|
Jeffrey Walton
|
0a87c88509
|
ANother AppVeyor attempt
Take 1 in this series
|
2017-08-03 19:13:29 -04:00 |
|
Jeffrey Walton
|
ef080dee99
|
This revert commit ac513c0. It broke AppVeyor worse than before.
Also see https://stackoverflow.com/questions/45474857/why-does-appveyor-use-vs2010-tools-for-vs2015-image
|
2017-08-03 01:42:40 -04:00 |
|
Jeffrey Walton
|
ac513c06f8
|
Test importing property sheets before project's global properties
|
2017-08-03 01:14:20 -04:00 |
|
Jeffrey Walton
|
a6acb45219
|
Suppress warnings C4231, C4355 and C4505 (Issue 412)
This should not cross-pollinate like when they were present in config.h
|
2017-08-02 23:21:25 -04:00 |
|
Jeffrey Walton
|
5583c34b46
|
Update fork *.vcxproject files
|
2017-08-02 22:21:15 -04:00 |
|
Jeffrey Walton
|
77d2e4eaf5
|
Add AppVeyor rule to makefile
This should sidestep some problems we are experiencing with AppVeyor during x64 builds. Specifically, the missing VCUpgrade.exe and the poor job it does when upgrading our project for the platform\'s tools.
This recipe takes cryptlib.vcxproj and cryptest.vcxproj, and copies it into TestScripts. This ensures TestScripts always has the latest Visual Studio project files. Then, the recipe changes PlatformToolset to the undocumented $\(DefaultPlatformToolset\). Finally, our AppVeyor test script will copy TestScripts/*.vcxproj into PWD before executing MSbuild.
Also see http://stackoverflow.com/questions/43423761/cant-perform-64-bit-testing-under-appveyor, http://stackoverflow.com/questions/45452145/how-to-set-platformtoolset-property-from-msbuild and http://stackoverflow.com/questions/43441273/how-to-run-vcupgrade-before-appveyor-build
|
2017-08-02 22:01:16 -04:00 |