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

58 строки
3.1 KiB
CMake
Исходник Обычный вид История

first commit
2016-12-28 22:52:27 +03:00
# Find the DIA SDK path.
get_filename_component(VS_PATH32 "[HKEY_LOCAL_MACHINE\\SOFTWARE\\Microsoft\\VisualStudio\\14.0;InstallDir]" ABSOLUTE CACHE)
get_filename_component(VS_PATH64 "[HKEY_LOCAL_MACHINE\\SOFTWARE\\WOW6432Node\\Microsoft\\VisualStudio\\14.0;InstallDir]" ABSOLUTE CACHE)
# VS_PATH32 will be something like C:/Program Files (x86)/Microsoft Visual Studio 14.0/Common7/IDE
Enable to detect DIA SDK in VS2019 (#2136)
2019-05-23 21:25:14 +03:00
# Also look for in vs15 or vs16 install.
Use program files x86 environment variable when looking for vs15 install (#1785) Use program files x86 environment variable when looking for vs15 install
2018-12-21 21:08:04 +03:00
set(PROGRAMFILES_X86 "ProgramFiles(x86)")
Enable to detect DIA SDK in VS2019 (#2136)
2019-05-23 21:25:14 +03:00
set(VS_PATH32 "$ENV{${PROGRAMFILES_X86}}/Microsoft Visual Studio")
get_filename_component(VS15_C_PATH32 "${VS_PATH32}/2017/Community/Common7/IDE" ABSOLUTE CACHE)
get_filename_component(VS15_P_PATH32 "${VS_PATH32}/2017/Professional/Common7/IDE" ABSOLUTE CACHE)
get_filename_component(VS15_E_PATH32 "${VS_PATH32}/2017/Enterprise/Common7/IDE" ABSOLUTE CACHE)
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
Enable non-C VS installs (#2463) * Move to use vswhere for 2017/2019 and add const to make 2019 STL happy * Add hardcoded 2017 paths back as vswhere was not in 2017 from the beginning
2019-09-18 03:13:38 +03:00
# Starting in VS 15.2, vswhere is included.
# Unclear what the right component to search for is, might be Microsoft.VisualStudio.Component.VC.DiagnosticTools
# (although the friendly name of that is C++ profiling tools). The toolset is the most likely target.
execute_process(
COMMAND "${VS_PATH32}/Installer/vswhere.exe" -latest -prerelease -products * -requires Microsoft.VisualStudio.Component.VC.Tools.x86.x64 -property installationPath
OUTPUT_VARIABLE VSWHERE_LATEST
ERROR_QUIET
OUTPUT_STRIP_TRAILING_WHITESPACE
)
Enable detection of Win10 SDK from environment variable instead of registry (#1832) Fix typo
2019-01-11 22:01:45 +03:00
# Find the DIA SDK path, it will typically look something like this.
Enable to detect DIA SDK in VS2019 (#2136)
2019-05-23 21:25:14 +03:00
# C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\DIA SDK\include
Update to VS 2017 and CMake 3.11.2 (#1347) * Change build to prefer VS 2017 * Update supported cmake version * Remove -vs2017 from appveyor.yml
2018-06-09 03:36:55 +03:00
# C:\Program Files (x86)\Microsoft Visual Studio\2017\Enterprise\DIA SDK\include
Enable to detect DIA SDK in VS2019 (#2136)
2019-05-23 21:25:14 +03:00
# C:\Program Files (x86)\Microsoft Visual Studio 14.0\DIA SDK\include
first commit
2016-12-28 22:52:27 +03:00
find_path(DIASDK_INCLUDE_DIR # Set variable DIASDK_INCLUDE_DIR
dia2.h # Find a path with dia2.h
Enable non-C VS installs (#2463) * Move to use vswhere for 2017/2019 and add const to make 2019 STL happy * Add hardcoded 2017 paths back as vswhere was not in 2017 from the beginning
2019-09-18 03:13:38 +03:00
HINTS "${VSWHERE_LATEST}/DIA SDK/include"
Update to VS 2017 and CMake 3.11.2 (#1347) * Change build to prefer VS 2017 * Update supported cmake version * Remove -vs2017 from appveyor.yml
2018-06-09 03:36:55 +03:00
HINTS "${VS15_C_PATH32}/../../DIA SDK/include"
HINTS "${VS15_P_PATH32}/../../DIA SDK/include"
HINTS "${VS15_E_PATH32}/../../DIA SDK/include"
first commit
2016-12-28 22:52:27 +03:00
HINTS "${VS_PATH64}/../../DIA SDK/include"
Update to VS 2017 and CMake 3.11.2 (#1347) * Change build to prefer VS 2017 * Update supported cmake version * Remove -vs2017 from appveyor.yml
2018-06-09 03:36:55 +03:00
HINTS "${VS_PATH32}/../../DIA SDK/include"
first commit
2016-12-28 22:52:27 +03:00
DOC "path to DIA SDK header files"
)
if (CMAKE_GENERATOR MATCHES "Visual Studio.*Win64" )
find_library(DIASDK_GUIDS_LIBRARY NAMES diaguids.lib
HINTS ${DIASDK_INCLUDE_DIR}/../lib/amd64 )
elseif (CMAKE_GENERATOR MATCHES "Visual Studio.*ARM" )
find_library(DIASDK_GUIDS_LIBRARY NAMES diaguids.lib
HINTS ${DIASDK_INCLUDE_DIR}/../lib/arm )
else (CMAKE_GENERATOR MATCHES "Visual Studio.*Win64" )
find_library(DIASDK_GUIDS_LIBRARY NAMES diaguids.lib
HINTS ${DIASDK_INCLUDE_DIR}/../lib )
endif (CMAKE_GENERATOR MATCHES "Visual Studio.*Win64" )
set(DIASDK_LIBRARIES ${DIASDK_GUIDS_LIBRARY})
set(DIASDK_INCLUDE_DIRS ${DIASDK_INCLUDE_DIR})
include(FindPackageHandleStandardArgs)
# handle the QUIETLY and REQUIRED arguments and set DIASDK_FOUND to TRUE
# if all listed variables are TRUE
find_package_handle_standard_args(DIASDK DEFAULT_MSG
DIASDK_LIBRARIES DIASDK_INCLUDE_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
mark_as_advanced(DIASDK_INCLUDE_DIRS DIASDK_LIBRARIES)