view .appveyor.yml @ 356:e10d30c67eff

Attempt to disentangle problems with 32-/64-bit build image compatibility
author Chris Cannam
date Thu, 24 Oct 2019 11:14:27 +0100
parents 0b3c180d5e08
children
line wrap: on
line source
# We currently use VS2017 for 32-bit and VS2019 image for 64-bit
# builds. This is pending updating our 32-bit (MinGW) library
# compatibility for MinGW 7.x.
#
image:
  - Visual Studio 2017
  - Visual Studio 2019

configuration:
  - Release

install:
  - cinst --allow-empty-checksums smlnj
  - cinst hg
  - ps: '"[hostfingerprints]" | Out-File -Encoding "ASCII" -Append $env:USERPROFILE\mercurial.ini'
  - ps: '"code.soundsoftware.ac.uk = C7:27:7E:2C:1E:67:62:90:E9:8D:27:52:66:30:E6:FE:D4:2C:C5:30" | Out-File -Encoding "ASCII" -Append $env:USERPROFILE\mercurial.ini'
  - ps: '"[hostsecurity]" | Out-File -Encoding "ASCII" -Append $env:USERPROFILE\mercurial.ini'
  - ps: '"code.soundsoftware.ac.uk = code.soundsoftware.ac.uk:fingerprints=sha256:AF:67:D8:D6:D8:2F:28:FF:B9:1A:4D:CD:6A:93:25:EC:9E:47:9E:0E:E7:F1:FD:0B:97:B4:7C:D5:FA:2E:10:73" | Out-File -Encoding "ASCII" -Append $env:USERPROFILE\mercurial.ini'

for:

-
  matrix:
    only:
      - image: Visual Studio 2017
      
  build_script:
    - deploy\win\build-32.bat

-
  matrix:
    only:
      - image: Visual Studio 2019
      
  build_script:
    - deploy\win\build-64.bat