10215300402
/
LevelDB-course-Lab
forked from building_data_management_systems.Xuanzhou.2024Fall.DaSE/leveldb_base
1
0
Fork 0
Code Issues 0 Pull Requests 0 Releases 0 Wiki Activity
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
314 Commits
2 Branches
1.9 MiB
Tree: 1c58902bdc
Branches Tags
${ item.name }
Create branch ${ searchTerm }
from '1c58902bdc'
${ noResults }
LevelDB-course-Lab/.appveyor.yml

36 lines
1.0 KiB
Raw Normal View History

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
5 years ago
​
​
​
​
​
​
​
​
​
Move CI to Visual Studio 2019. PiperOrigin-RevId: 279785825
5 years ago
​
​
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
5 years ago
​
​
​
​
​
​
​
​
​
​
​
​
Move CI to Visual Studio 2019. PiperOrigin-RevId: 279785825
5 years ago
​
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
5 years ago
Move CI to Visual Studio 2019. PiperOrigin-RevId: 279785825
5 years ago
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
5 years ago
​
​
​
​
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
5 years ago
 
  1. # Build matrix / environment variables are explained on:

  2. # https://www.appveyor.com/docs/appveyor-yml/

  3. # This file can be validated on: https://ci.appveyor.com/tools/validate-yaml

  4. 

  5. version: "{build}"

  6. 

  7. environment:

  8.   matrix:

  9.     # AppVeyor currently has no custom job name feature.

  10.     # http://help.appveyor.com/discussions/questions/1623-can-i-provide-a-friendly-name-for-jobs

  11.     - JOB: Visual Studio 2019

  12.       APPVEYOR_BUILD_WORKER_IMAGE: Visual Studio 2019

  13.       CMAKE_GENERATOR: Visual Studio 16 2019

  14. 

  15. platform:

  16.   - x86

  17.   - x64

  18. 

  19. configuration:

  20.   - RelWithDebInfo

  21.   - Debug

  22. 

  23. build_script:

  24.   - git submodule update --init --recursive

  25.   - mkdir build

  26.   - cd build

  27.   - if "%platform%"=="x86" (set CMAKE_GENERATOR_PLATFORM="Win32")

  28.       else (set CMAKE_GENERATOR_PLATFORM="%platform%")

  29.   - cmake --version

  30.   - cmake .. -G "%CMAKE_GENERATOR%" -A "%CMAKE_GENERATOR_PLATFORM%"

  31.       -DCMAKE_CONFIGURATION_TYPES="%CONFIGURATION%"

  32.   - cmake --build . --config "%CONFIGURATION%"

  33.   - cd ..

  34. 

  35. test_script:

  36.   - cd build && ctest --verbose --build-config "%CONFIGURATION%" && cd ..