15 Commits (c793374f16071261c25c80fa88cb35a57f630630)

Author SHA1 Message Date
  Eric Haszlakiewicz 1cb56e705f Put the most recent image first in appveyor builds. 3 years ago
  Eric Haszlakiewicz 1763edaba3 Skip most "Release" builds. s/b_config/CONFIGURATION/ to fix artifact creation. 3 years ago
  Eric Haszlakiewicz a5fed59756 There doesn't seem to be a way to extend the appveyor build matrix for just one image, so instead list a whole bunch of excluded builds. 3 years ago
  Eric Haszlakiewicz 0910e18bbd Use the newer appveyor images to build for VS2017 and VS2019. Trim the number of builds we do. 3 years ago
  Björn Esser 37355cf0e6
Fix line terminators to be UNIX. 5 years ago
  Unmanned Player f2e991a341 The real CMake support 7 years ago
  Eric Haszlakiewicz 7038bb8061 Try the appveyor changes again, using %Configuration% instead of "Debug" 7 years ago
  Eric Haszlakiewicz dfc0fddf22 Include the json-c.lib, .pdb and .exp files in the zip file created by the appveyor build, since it seems they're needed for linking and debugging. 7 years ago
  Eric Haszlakiewicz cfbdf7757b The new cmake-generated VS builds now generate a dynamic .dll instead of a .lib 8 years ago
  Eric Haszlakiewicz 139eb64b43 For appveyor builds, json_config.h is actually generated in the "include" directory. 8 years ago
  Eric Haszlakiewicz 8899f3fbfb Add a "cmake ." line to the appveyor build file to try to get it working again. 8 years ago
  James Myatt 239c146a4b Appveyor: Visual Studio v140 no longer fails 10 years ago
  James Myatt fd43c2b99a Appveyor: Create artefact with library and include files only 10 years ago
  James Myatt 17e11e2c92 Appveyor: Allow failing builds against newest toolset 10 years ago
  James Myatt f6f8436e97 Add initial version of Appveyor build script 10 years ago