Initial import of code.

Author: tangent-vector

.gitignore

@@ -0,0 +1,26 @@
+*.exe
+*.pdb
+.vs
+*.VC.opendb
+*.VC.db
+*.vcxproj.user
+*.sdf
+bin/
+intermediate/
+
+# files generated by test runner
+*.actual
+*.hlsl.expected
+*.fx.expected
+*.glsl.expected
+*.vert.expected
+*.frag.expected
+*.geom.expected
+*.tesc.expected
+*.tese.expected
+*.comp.expected
+*.expected.png
+*.actual.png
+
+# files generated by other shader compilers
+*.spv

LICENSE

@@ -1,6 +1,6 @@
 MIT License
 
-Copyright (c) 2017 shader-slang
+Copyright (c) 2016, Carnegie Mellon University and NVIDIA Corporation
 
 Permission is hereby granted, free of charge, to any person obtaining a copy
 of this software and associated documentation files (the "Software"), to deal

README.md

@@ -1,2 +1,38 @@
-# slang
-Making it easier to work with shaders
+# Slang
+
+Slang is a library for compiling real-time shader code.
+It can be used with either existing HLSL or GLSL code, or with code written directly in Slang.
+The library provides a variety of services that application developers can use to put together the shader compilation workflow they want.
+
+Services provided by the Slang library include:
+
+* Slang can scan ordinary HLSL or GLSL code that neglects to include `register` or `layout` bindings and "rewrite" that code to include explicit bindings for all shader parameters. This lets you write simple and clean code, but still get deterministic binding locations.
+
+* Slang provides a full reflection API for shader parameters, with a uniform interface across HLSL, GLSL, and Slang. The reflection system does not silently drop unused/"dead" parameters, and it can even be used on libraries of shader code without compiling any entry points.
+
+* *Work in progress:* Slang supports cross-compilation of either HLSL or Slang code to GLSL.
+
+* You can directly get HLSL or GLSL source code as output from Slang, or you can let the library invoke lower-level code generation for you to get back DXBC or SPIR-V (DXIL support to come).
+
+## Documentation
+
+TODO
+
+## Getting Started
+
+TODO
+
+## Testing
+
+TODO
+
+## Contributing
+
+TODO
+
+## Contributors
+
+* Yong He
+* Haomin Long
+* Teguh Hofstee
+* Tim Foley

build/slang-build.props

@@ -0,0 +1,11 @@
+<?xml version="1.0" encoding="utf-8"?>
+<Project ToolsVersion="4.0" xmlns="http://schemas.microsoft.com/developer/msbuild/2003">
+  <ImportGroup Label="PropertySheets" />
+  <PropertyGroup Label="UserMacros" />
+  <PropertyGroup>
+    <OutDir>$(SolutionDir)bin\$(PlatformShortName)\$(Configuration)\</OutDir>
+    <IntDir>$(SolutionDir)intermediate\$(PlatformShortName)\$(Configuration)\$(ProjectName)\</IntDir>
+  </PropertyGroup>
+  <ItemDefinitionGroup />
+  <ItemGroup />
+</Project>

examples/hello/README.md

@@ -0,0 +1,9 @@
+Spire "Hello World" Example
+===========================
+
+The goal of this example is to demonstrate an almost minimal application that uses Spire for shading, and D3D11 for rendering.
+
+The `hello.spire` file contains a simple declaration of a Spire *shader module*, along with a *pipeline declaration* that will be used for mapping shader code to the capabilities of the "engine" (in this case, just vertex and fragment shaders).
+The `hello.cpp` file contains the C++ application code, showing how to use the Spire C API to load and compile the shader code, and construct a (trivial) executable shader from Spire modules.
+
+Note that this example is not intended to demonstrate good practices for integrating Spire into a production engine; the goal is merely to use the minimum amount of code possible to demonstrate a complete applicaiton that uses Spire.