microsoft
/
DirectXShaderCompiler
зеркало из https://github.com/microsoft/DirectXShaderCompiler.git
1
0
Форкнуть 0
Код Задачи Пакеты Проекты Релизы Вики Активность
DirectXShaderCompiler/appveyor.yml

40 строки
960 B
YAML
Исходник Обычный вид История

Add support for AppVeyor continuous integration (#131) This commit makes the necessary changes to run the project with AppVeyor CI. The `appveyor.yml` file contains the configuration settings for the build. Currently we only build x64-Debug, but we can build the full x32/x64-Debug/Release matrix by adding a few lines to the config. The remaining changes are somewhat tied to the specifics of how appveyor provisions the build machines. The standard VS2015 machines build on Windows Server 2012. We can build on these machines, but cannot run tests because we require d3d12.dll which is not available on Windows Server 2012. However, it is present on Windows Server 2016, but appveyor only provides VS2017 on those machines. So part of the changes are to allow the compiler to build with VS2017 so we can run tests as part of CI. The `appveyor_setup.ps1` script installs the WDK as part of the build. This is the only extra software we need. It is actually installed on the VS2015 build machines, but not our VS2017 build machines. Perhaps we can get them to install it by default and then this script can go away. The `appveyor_test.ps1` script runs the taef tests and then reports the results to appveyor so they can be displayed on the "Tests" tab. As a side effect of this work, We can now use the latest cmake (3.7.2) for our own builds! The key seems to be setting `-DCMAKE_SYSTEM_VERSION=10.0.14393.0` to ensure that we pick up the correct SDK.
2017-03-14 02:21:15 +03:00
version: 1.0.{build}
Upload artifacts in Appveyor Artifacts page (#641)
2017-09-22 19:30:33 +03:00
Add support for AppVeyor continuous integration (#131) This commit makes the necessary changes to run the project with AppVeyor CI. The `appveyor.yml` file contains the configuration settings for the build. Currently we only build x64-Debug, but we can build the full x32/x64-Debug/Release matrix by adding a few lines to the config. The remaining changes are somewhat tied to the specifics of how appveyor provisions the build machines. The standard VS2015 machines build on Windows Server 2012. We can build on these machines, but cannot run tests because we require d3d12.dll which is not available on Windows Server 2012. However, it is present on Windows Server 2016, but appveyor only provides VS2017 on those machines. So part of the changes are to allow the compiler to build with VS2017 so we can run tests as part of CI. The `appveyor_setup.ps1` script installs the WDK as part of the build. This is the only extra software we need. It is actually installed on the VS2015 build machines, but not our VS2017 build machines. Perhaps we can get them to install it by default and then this script can go away. The `appveyor_test.ps1` script runs the taef tests and then reports the results to appveyor so they can be displayed on the "Tests" tab. As a side effect of this work, We can now use the latest cmake (3.7.2) for our own builds! The key seems to be setting `-DCMAKE_SYSTEM_VERSION=10.0.14393.0` to ensure that we pick up the correct SDK.
2017-03-14 02:21:15 +03:00
image: Visual Studio 2017
platform: x64
configuration: Debug
Upload artifacts in Appveyor Artifacts page (#641)
2017-09-22 19:30:33 +03:00
Add support for AppVeyor continuous integration (#131) This commit makes the necessary changes to run the project with AppVeyor CI. The `appveyor.yml` file contains the configuration settings for the build. Currently we only build x64-Debug, but we can build the full x32/x64-Debug/Release matrix by adding a few lines to the config. The remaining changes are somewhat tied to the specifics of how appveyor provisions the build machines. The standard VS2015 machines build on Windows Server 2012. We can build on these machines, but cannot run tests because we require d3d12.dll which is not available on Windows Server 2012. However, it is present on Windows Server 2016, but appveyor only provides VS2017 on those machines. So part of the changes are to allow the compiler to build with VS2017 so we can run tests as part of CI. The `appveyor_setup.ps1` script installs the WDK as part of the build. This is the only extra software we need. It is actually installed on the VS2015 build machines, but not our VS2017 build machines. Perhaps we can get them to install it by default and then this script can go away. The `appveyor_test.ps1` script runs the taef tests and then reports the results to appveyor so they can be displayed on the "Tests" tab. As a side effect of this work, We can now use the latest cmake (3.7.2) for our own builds! The key seems to be setting `-DCMAKE_SYSTEM_VERSION=10.0.14393.0` to ensure that we pick up the correct SDK.
2017-03-14 02:21:15 +03:00
clone_folder: c:\projects\DirectXShaderCompiler
Upload artifacts in Appveyor Artifacts page (#641)
2017-09-22 19:30:33 +03:00
clone_depth: 1
Add support for AppVeyor continuous integration (#131) This commit makes the necessary changes to run the project with AppVeyor CI. The `appveyor.yml` file contains the configuration settings for the build. Currently we only build x64-Debug, but we can build the full x32/x64-Debug/Release matrix by adding a few lines to the config. The remaining changes are somewhat tied to the specifics of how appveyor provisions the build machines. The standard VS2015 machines build on Windows Server 2012. We can build on these machines, but cannot run tests because we require d3d12.dll which is not available on Windows Server 2012. However, it is present on Windows Server 2016, but appveyor only provides VS2017 on those machines. So part of the changes are to allow the compiler to build with VS2017 so we can run tests as part of CI. The `appveyor_setup.ps1` script installs the WDK as part of the build. This is the only extra software we need. It is actually installed on the VS2015 build machines, but not our VS2017 build machines. Perhaps we can get them to install it by default and then this script can go away. The `appveyor_test.ps1` script runs the taef tests and then reports the results to appveyor so they can be displayed on the "Tests" tab. As a side effect of this work, We can now use the latest cmake (3.7.2) for our own builds! The key seems to be setting `-DCMAKE_SYSTEM_VERSION=10.0.14393.0` to ensure that we pick up the correct SDK.
2017-03-14 02:21:15 +03:00
environment:
HLSL_SRC_DIR: c:\projects\DirectXShaderCompiler
Upload artifacts in Appveyor Artifacts page (#641)
2017-09-22 19:30:33 +03:00
HLSL_BLD_DIR: c:\projects\DirectXShaderCompiler\build
Add support for AppVeyor continuous integration (#131) This commit makes the necessary changes to run the project with AppVeyor CI. The `appveyor.yml` file contains the configuration settings for the build. Currently we only build x64-Debug, but we can build the full x32/x64-Debug/Release matrix by adding a few lines to the config. The remaining changes are somewhat tied to the specifics of how appveyor provisions the build machines. The standard VS2015 machines build on Windows Server 2012. We can build on these machines, but cannot run tests because we require d3d12.dll which is not available on Windows Server 2012. However, it is present on Windows Server 2016, but appveyor only provides VS2017 on those machines. So part of the changes are to allow the compiler to build with VS2017 so we can run tests as part of CI. The `appveyor_setup.ps1` script installs the WDK as part of the build. This is the only extra software we need. It is actually installed on the VS2015 build machines, but not our VS2017 build machines. Perhaps we can get them to install it by default and then this script can go away. The `appveyor_test.ps1` script runs the taef tests and then reports the results to appveyor so they can be displayed on the "Tests" tab. As a side effect of this work, We can now use the latest cmake (3.7.2) for our own builds! The key seems to be setting `-DCMAKE_SYSTEM_VERSION=10.0.14393.0` to ensure that we pick up the correct SDK.
2017-03-14 02:21:15 +03:00
install:
- ps: c:\projects\DirectXShaderCompiler\utils\appveyor\appveyor_setup.ps1
[spirv] Use git submodules for SPIR-V dependency projects (#455)
2017-07-24 23:12:48 +03:00
- git submodule update --init --recursive
Add support for AppVeyor continuous integration (#131) This commit makes the necessary changes to run the project with AppVeyor CI. The `appveyor.yml` file contains the configuration settings for the build. Currently we only build x64-Debug, but we can build the full x32/x64-Debug/Release matrix by adding a few lines to the config. The remaining changes are somewhat tied to the specifics of how appveyor provisions the build machines. The standard VS2015 machines build on Windows Server 2012. We can build on these machines, but cannot run tests because we require d3d12.dll which is not available on Windows Server 2012. However, it is present on Windows Server 2016, but appveyor only provides VS2017 on those machines. So part of the changes are to allow the compiler to build with VS2017 so we can run tests as part of CI. The `appveyor_setup.ps1` script installs the WDK as part of the build. This is the only extra software we need. It is actually installed on the VS2015 build machines, but not our VS2017 build machines. Perhaps we can get them to install it by default and then this script can go away. The `appveyor_test.ps1` script runs the taef tests and then reports the results to appveyor so they can be displayed on the "Tests" tab. As a side effect of this work, We can now use the latest cmake (3.7.2) for our own builds! The key seems to be setting `-DCMAKE_SYSTEM_VERSION=10.0.14393.0` to ensure that we pick up the correct SDK.
2017-03-14 02:21:15 +03:00
Upload artifacts in Appveyor Artifacts page (#641)
2017-09-22 19:30:33 +03:00
before_build:
- cmd: call utils\hct\hctstart %HLSL_SRC_DIR% %HLSL_BLD_DIR%
Add support for AppVeyor continuous integration (#131) This commit makes the necessary changes to run the project with AppVeyor CI. The `appveyor.yml` file contains the configuration settings for the build. Currently we only build x64-Debug, but we can build the full x32/x64-Debug/Release matrix by adding a few lines to the config. The remaining changes are somewhat tied to the specifics of how appveyor provisions the build machines. The standard VS2015 machines build on Windows Server 2012. We can build on these machines, but cannot run tests because we require d3d12.dll which is not available on Windows Server 2012. However, it is present on Windows Server 2016, but appveyor only provides VS2017 on those machines. So part of the changes are to allow the compiler to build with VS2017 so we can run tests as part of CI. The `appveyor_setup.ps1` script installs the WDK as part of the build. This is the only extra software we need. It is actually installed on the VS2015 build machines, but not our VS2017 build machines. Perhaps we can get them to install it by default and then this script can go away. The `appveyor_test.ps1` script runs the taef tests and then reports the results to appveyor so they can be displayed on the "Tests" tab. As a side effect of this work, We can now use the latest cmake (3.7.2) for our own builds! The key seems to be setting `-DCMAKE_SYSTEM_VERSION=10.0.14393.0` to ensure that we pick up the correct SDK.
2017-03-14 02:21:15 +03:00
Upload artifacts in Appveyor Artifacts page (#641)
2017-09-22 19:30:33 +03:00
build_script:
- cmd: call utils\hct\hctbuild -%PLATFORM% -%CONFIGURATION% -vs2017 -spirvtest
Add support for AppVeyor continuous integration (#131) This commit makes the necessary changes to run the project with AppVeyor CI. The `appveyor.yml` file contains the configuration settings for the build. Currently we only build x64-Debug, but we can build the full x32/x64-Debug/Release matrix by adding a few lines to the config. The remaining changes are somewhat tied to the specifics of how appveyor provisions the build machines. The standard VS2015 machines build on Windows Server 2012. We can build on these machines, but cannot run tests because we require d3d12.dll which is not available on Windows Server 2012. However, it is present on Windows Server 2016, but appveyor only provides VS2017 on those machines. So part of the changes are to allow the compiler to build with VS2017 so we can run tests as part of CI. The `appveyor_setup.ps1` script installs the WDK as part of the build. This is the only extra software we need. It is actually installed on the VS2015 build machines, but not our VS2017 build machines. Perhaps we can get them to install it by default and then this script can go away. The `appveyor_test.ps1` script runs the taef tests and then reports the results to appveyor so they can be displayed on the "Tests" tab. As a side effect of this work, We can now use the latest cmake (3.7.2) for our own builds! The key seems to be setting `-DCMAKE_SYSTEM_VERSION=10.0.14393.0` to ensure that we pick up the correct SDK.
2017-03-14 02:21:15 +03:00
Upload artifacts in Appveyor Artifacts page (#641)
2017-09-22 19:30:33 +03:00
test_script:
- cmd: powershell utils\appveyor\appveyor_test.ps1
- cmd: call utils\hct\hcttest spirv_only
Zip artifacts built on Appveyor (#647)
2017-09-25 19:44:58 +03:00
after_test:
- cmd: cd build\%CONFIGURATION%\bin
- cmd: 7z a artifacts.zip d*.exe d*.dll HLSLHost.exe
Upload artifacts in Appveyor Artifacts page (#641)
2017-09-22 19:30:33 +03:00
artifacts:
Zip artifacts built on Appveyor (#647)
2017-09-25 19:44:58 +03:00
- path: build\$(configuration)\bin\artifacts.zip
Add support for AppVeyor continuous integration (#131) This commit makes the necessary changes to run the project with AppVeyor CI. The `appveyor.yml` file contains the configuration settings for the build. Currently we only build x64-Debug, but we can build the full x32/x64-Debug/Release matrix by adding a few lines to the config. The remaining changes are somewhat tied to the specifics of how appveyor provisions the build machines. The standard VS2015 machines build on Windows Server 2012. We can build on these machines, but cannot run tests because we require d3d12.dll which is not available on Windows Server 2012. However, it is present on Windows Server 2016, but appveyor only provides VS2017 on those machines. So part of the changes are to allow the compiler to build with VS2017 so we can run tests as part of CI. The `appveyor_setup.ps1` script installs the WDK as part of the build. This is the only extra software we need. It is actually installed on the VS2015 build machines, but not our VS2017 build machines. Perhaps we can get them to install it by default and then this script can go away. The `appveyor_test.ps1` script runs the taef tests and then reports the results to appveyor so they can be displayed on the "Tests" tab. As a side effect of this work, We can now use the latest cmake (3.7.2) for our own builds! The key seems to be setting `-DCMAKE_SYSTEM_VERSION=10.0.14393.0` to ensure that we pick up the correct SDK.
2017-03-14 02:21:15 +03:00
notifications:
- provider: GitHubPullRequest
on_build_success: true
on_build_failure: true
on_build_status_changed: true