server-skynet-source-3rd-je.../.appveyor.yml

version: '{build}'

environment:
  matrix:
  - MSYSTEM: MINGW64
    CPU: x86_64
    MSVC: amd64
    CONFIG_FLAGS: --enable-debug
  - MSYSTEM: MINGW64
    CPU: x86_64
    CONFIG_FLAGS: --enable-debug
  - MSYSTEM: MINGW32
    CPU: i686
    MSVC: x86
    CONFIG_FLAGS: --enable-debug
  - MSYSTEM: MINGW32
    CPU: i686
    CONFIG_FLAGS: --enable-debug
  - MSYSTEM: MINGW64
    CPU: x86_64
    MSVC: amd64
  - MSYSTEM: MINGW64
    CPU: x86_64
  - MSYSTEM: MINGW32
    CPU: i686
    MSVC: x86
  - MSYSTEM: MINGW32
    CPU: i686

install:
  - set PATH=c:\msys64\%MSYSTEM%\bin;c:\msys64\usr\bin;%PATH%
  - if defined MSVC call "c:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\vcvarsall.bat" %MSVC%
  - if defined MSVC pacman --noconfirm -Rsc mingw-w64-%CPU%-gcc gcc
  - pacman --noconfirm -Suy mingw-w64-%CPU%-make

build_script:
  - bash -c "autoconf"
  - bash -c "./configure $CONFIG_FLAGS"
  - mingw32-make
  - file lib/jemalloc.dll
  - mingw32-make tests
  - mingw32-make -k check
Add an AppVeyor config This builds jemalloc and runs all checks with: - MSVC 2015 64-bits - MSVC 2015 32-bits - MINGW64 (from msys2) - MINGW32 (from msys2) Normally, AppVeyor configs are named appveyor.yml, but it is possible to configure the .yml file name in the AppVeyor project settings such that the file stays "hidden", like typical travis configs. 2016-06-09 16:10:16 +08:00			`version: '{build}'`

			`environment:`
			`matrix:`
			`- MSYSTEM: MINGW64`
			`CPU: x86_64`
			`MSVC: amd64`
Reorder the configs for AppVeyor. Enable-debug and 64-bit runs tend to be more relevant. Run them first. 2019-07-14 11:27:15 +08:00			`CONFIG_FLAGS: --enable-debug`
			`- MSYSTEM: MINGW64`
			`CPU: x86_64`
			`CONFIG_FLAGS: --enable-debug`
Add an AppVeyor config This builds jemalloc and runs all checks with: - MSVC 2015 64-bits - MSVC 2015 32-bits - MINGW64 (from msys2) - MINGW32 (from msys2) Normally, AppVeyor configs are named appveyor.yml, but it is possible to configure the .yml file name in the AppVeyor project settings such that the file stays "hidden", like typical travis configs. 2016-06-09 16:10:16 +08:00			`- MSYSTEM: MINGW32`
			`CPU: i686`
			`MSVC: x86`
Reorder the configs for AppVeyor. Enable-debug and 64-bit runs tend to be more relevant. Run them first. 2019-07-14 11:27:15 +08:00			`CONFIG_FLAGS: --enable-debug`
Add an AppVeyor config This builds jemalloc and runs all checks with: - MSVC 2015 64-bits - MSVC 2015 32-bits - MINGW64 (from msys2) - MINGW32 (from msys2) Normally, AppVeyor configs are named appveyor.yml, but it is possible to configure the .yml file name in the AppVeyor project settings such that the file stays "hidden", like typical travis configs. 2016-06-09 16:10:16 +08:00			`- MSYSTEM: MINGW32`
			`CPU: i686`
Reorder the configs for AppVeyor. Enable-debug and 64-bit runs tend to be more relevant. Run them first. 2019-07-14 11:27:15 +08:00			`CONFIG_FLAGS: --enable-debug`
CI: Run --enable-debug builds on windows This will hopefully catch some windows-specific bugs. 2017-02-01 08:44:57 +08:00			`- MSYSTEM: MINGW64`
			`CPU: x86_64`
			`MSVC: amd64`
Reorder the configs for AppVeyor. Enable-debug and 64-bit runs tend to be more relevant. Run them first. 2019-07-14 11:27:15 +08:00			`- MSYSTEM: MINGW64`
			`CPU: x86_64`
CI: Run --enable-debug builds on windows This will hopefully catch some windows-specific bugs. 2017-02-01 08:44:57 +08:00			`- MSYSTEM: MINGW32`
			`CPU: i686`
			`MSVC: x86`
			`- MSYSTEM: MINGW32`
			`CPU: i686`
Add an AppVeyor config This builds jemalloc and runs all checks with: - MSVC 2015 64-bits - MSVC 2015 32-bits - MINGW64 (from msys2) - MINGW32 (from msys2) Normally, AppVeyor configs are named appveyor.yml, but it is possible to configure the .yml file name in the AppVeyor project settings such that the file stays "hidden", like typical travis configs. 2016-06-09 16:10:16 +08:00
			`install:`
			`- set PATH=c:\msys64\%MSYSTEM%\bin;c:\msys64\usr\bin;%PATH%`
			`- if defined MSVC call "c:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\vcvarsall.bat" %MSVC%`
			`- if defined MSVC pacman --noconfirm -Rsc mingw-w64-%CPU%-gcc gcc`
			`- pacman --noconfirm -Suy mingw-w64-%CPU%-make`

			`build_script:`
			`- bash -c "autoconf"`
CI: Run --enable-debug builds on windows This will hopefully catch some windows-specific bugs. 2017-02-01 08:44:57 +08:00			`- bash -c "./configure $CONFIG_FLAGS"`
Do not build in parallel on AppVeyor. The compiler database used by MSVC is increasingly becoming corrupt, presumably due to concurrency-related corruption, despite the -FS compiler flag being specified as recommended. 2017-05-12 11:22:48 +08:00			`- mingw32-make`
Add an AppVeyor config This builds jemalloc and runs all checks with: - MSVC 2015 64-bits - MSVC 2015 32-bits - MINGW64 (from msys2) - MINGW32 (from msys2) Normally, AppVeyor configs are named appveyor.yml, but it is possible to configure the .yml file name in the AppVeyor project settings such that the file stays "hidden", like typical travis configs. 2016-06-09 16:10:16 +08:00			`- file lib/jemalloc.dll`
Do not build in parallel on AppVeyor. The compiler database used by MSVC is increasingly becoming corrupt, presumably due to concurrency-related corruption, despite the -FS compiler flag being specified as recommended. 2017-05-12 11:22:48 +08:00			`- mingw32-make tests`
Add an AppVeyor config This builds jemalloc and runs all checks with: - MSVC 2015 64-bits - MSVC 2015 32-bits - MINGW64 (from msys2) - MINGW32 (from msys2) Normally, AppVeyor configs are named appveyor.yml, but it is possible to configure the .yml file name in the AppVeyor project settings such that the file stays "hidden", like typical travis configs. 2016-06-09 16:10:16 +08:00			`- mingw32-make -k check`