* Much easier way to expose download links in README
The previous instructions would have users go to appveyor and click on the platform and find the "Artifacts" tab and click download. I have added direct links to the download zip files.
* Update artifact location link, and move the section to the top.
* back to direct links. Added ?branch=master&pr=false.
At some point, the capitalization of the Microsoft organization name on
github was changed to lowercase to better match precedent. Update the
links in README.md to reflect this.
Moved logistics and designs to the wiki page. Now the doc is only
for HLSL to SPIR-V mappings.
Also link to the doc and wiki page in the main README.md.
Use the new CMake build support in VS2017 to build without having to run cmake
separately. Removes the need to download cmake separately.
By default binaries are built in:
%LOCALAPPDATA%\CMakeBuild\DirectXShaderCompiler\build\{build-flavor}
Build settings can be changed by modifying CMakeSettings.json.
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.
Improve new developer experience
Update README and hctstart.cmd tools to help new developers.
Update README
* Add instructions on how to setup the build environment
from the command line.
* Add note to install common tools for c++ to get the atl headers.
* Change cmake download to point to cmake 3.4.3. Version 3.4 did
not work for me (it could not find the Visual Studio compiler tools).
Modify hctstart.cmd
* Explicitly check for the d3d12.h header from the 10240 windows kit.
Without this early check we get a build error much later.
* Check for cmake version 3.4.3 and warn if not found.
Update gitignore for visual studio code temporary files.
Ehsan
Greg Roth
Helena Kotas
Chas. Boyd
Ehsan
Tex Riddell
Lei Zhang
Marcelo Lopez Ruiz
Thomas Raoux
Justin Holewinski
David Peixotto