leveldb/.appveyor.yml

# Build matrix / environment variables are explained on:
# https://www.appveyor.com/docs/appveyor-yml/
# This file can be validated on: https://ci.appveyor.com/tools/validate-yaml

version: "{build}"

environment:
  matrix:
    # AppVeyor currently has no custom job name feature.
    # http://help.appveyor.com/discussions/questions/1623-can-i-provide-a-friendly-name-for-jobs
    - JOB: Visual Studio 2017
      APPVEYOR_BUILD_WORKER_IMAGE: Visual Studio 2017
      CMAKE_GENERATOR: Visual Studio 15 2017

platform:
  - x86
  - x64

configuration:
  - RelWithDebInfo
  - Debug

build_script:
  - git submodule update --init --recursive
  - mkdir build
  - cd build
  - if "%platform%"=="x64" set CMAKE_GENERATOR=%CMAKE_GENERATOR% Win64
  - cmake --version
  - cmake .. -G "%CMAKE_GENERATOR%"
      -DCMAKE_CONFIGURATION_TYPES="%CONFIGURATION%"
  - cmake --build . --config "%CONFIGURATION%"
  - cd ..

test_script:
  - cd build && ctest --verbose --build-config "%CONFIGURATION%" && cd ..
Added native support for Windows. This change adds a native Windows port (port_windows.h) and a Windows Env (WindowsEnv). Note1: "small" is defined when including <Windows.h> so some parameters were renamed to avoid conflict. Note2: leveldb::Env defines the method: "DeleteFile" which is also a constant defined when including <Windows.h>. The solution was to ensure this macro is defined in env.h which forces the function, when compiled, to be either DeleteFileA or DeleteFileW when building for MBCS or UNICODE respectively. This resolves #519 on GitHub. ------------- Created by MOE: https://github.com/google/moe MOE_MIGRATED_REVID=236364778 2019-03-01 13:12:01 -08:00			`# Build matrix / environment variables are explained on:`
			`# https://www.appveyor.com/docs/appveyor-yml/`
			`# This file can be validated on: https://ci.appveyor.com/tools/validate-yaml`

			`version: "{build}"`

			`environment:`
			`matrix:`
			`# AppVeyor currently has no custom job name feature.`
			`# http://help.appveyor.com/discussions/questions/1623-can-i-provide-a-friendly-name-for-jobs`
			`- JOB: Visual Studio 2017`
			`APPVEYOR_BUILD_WORKER_IMAGE: Visual Studio 2017`
			`CMAKE_GENERATOR: Visual Studio 15 2017`

			`platform:`
			`- x86`
			`- x64`

			`configuration:`
			`- RelWithDebInfo`
			`- Debug`

			`build_script:`
			`- git submodule update --init --recursive`
			`- mkdir build`
			`- cd build`
			`- if "%platform%"=="x64" set CMAKE_GENERATOR=%CMAKE_GENERATOR% Win64`
			`- cmake --version`
			`- cmake .. -G "%CMAKE_GENERATOR%"`
			`-DCMAKE_CONFIGURATION_TYPES="%CONFIGURATION%"`
			`- cmake --build . --config "%CONFIGURATION%"`
			`- cd ..`

			`test_script:`
Improve CI configuration. This CL fixes the following issues: * The Travis CI had the ctest invocation followed by a ";", so non-zero exit codes (indicating test failures) did not cause the build to fail. * The AppVeyor CI had the ctest invocation followed by a ";", causing an error on Windows, where "&" plays the role of ";" [1]. The Windows CI (AppVeyor) will still be red after this CL, as some of the tests are failing. However, this CL is a step forward, as it gets us from failing to start tests to running tests and recording success/error states. [1] https://docs.microsoft.com/en-us/previous-versions/windows/it-pro/windows-xp/bb490954(v=technet.10)#using-multiple-commands-and-conditional-processing-symbols ------------- Created by MOE: https://github.com/google/moe MOE_MIGRATED_REVID=236765633 2019-03-04 18:27:03 -08:00			`- cd build && ctest --verbose --build-config "%CONFIGURATION%" && cd ..`