Making it easier to work with shaders https://git.yummers.dev/slang.git/atom?h=master 2020-12-04T18:03:29+00:00 2020-12-04T18:03:29+00:00 jsmall-nvidia jsmall@nvidia.com 2020-12-04T18:03:29+00:00 urn:sha1:47ed0f68602a8ed0c425d2a4666969ad0db04ca6 * #include an absolute path didn't work - because paths were taken to always be relative. * Move reflection to reflection-api. * Slight reorg to pull out potentially Slang internal functions from the reflection API impls. * Remove visual studio projects * Fix for slang-binaries copy. * Add the visual studio projects in build/visual-studio * Remove miniz project. * Differentiate the linePath from the filePath. * Improve comment in premake5.lua + to kick of CI. * Kick CI. 2018-05-11T23:34:19+00:00 Tim Foley tfoleyNV@users.noreply.github.com 2018-05-11T23:34:19+00:00 urn:sha1:e2c2c220c642cc5f1c622f909d0ddfd22e6c04d4 * Generate Visual Studio projects using Premake This change adds a `premake5.lua` file that allows us to generate our Visual Studio solution using Premake 5 (https://premake.github.io/). The existing Visual Studio solution/projects are now replaced with the Premake-generated ones, and project contributors will be expected to update these by running premake after adding/removing files. I have *not* changed the Linux `Makefile` build at all, because that file is also used for things like running our tests, so that clobbering it with a premake-generated `Makefile` would break our continuous testing. Hopefully future changes can switch to a generated `Makefile` and perhaps even add an XCode project as well. Notes: * The `build/slang-build.props` file is no longer needed/used, so it has been removed. * The `slang-eval-test` test fixture wasn't following our naming conventions for its directory path, so it was updated to streamline the Premake build configuration work. This required changes to the `Makefile` as well * Some seemingly unncessary preprocessor definitions that were specified for `core` and `slang-glslang` have been dropped. We will see if anything breaks from that. * Possible fixup for Premake vpath issue Premake's `vpath` feature seems to be nondeterministic about the order it applies filters (because Lua isn't deterministic about the order of entries in a key/value table), and as a result we can end up in a weird case where it decides that a `foo.cpp.h` file matches the `**.cpp` filter (I'm not sure why) before it tests against the `**.h` filter. This change uses an (undocumented) Premake facility to set `vpath` using a list of singleton tables, which seems to fix the order in which things get tested. * Remove support for "single-file" build of Slang The `hello` example was the only bit of code that uses the "single-file" way of building Slang, and this had already run up against limitations of the Visual Studio compilers in its Debug|x64 build. Rather than mess with Premake to make it pass through the `/bigobj` linker flag that is needed to work around the issue, it makes more sense just to stop using/supporting the feature since we wouldn't want users to depend on it anyway (our documentation no longer refers to it). While I was at it I went ahead and made sure that the `SLANG_DYNAMIC` flag doesn't need to be set manually, so that instead there is a non-default `SLANG_STATIC` option (not that we have a static-library build of Slang at the moment). 2018-03-29T20:40:55+00:00 Tim Foley tfoleyNV@users.noreply.github.com 2018-03-29T20:40:55+00:00 urn:sha1:b61371d06c3ac18d1df6798b8042d4252485d935 Fixes #350 When the Slang project forked off from the Spire research effort, we renamed things as we went, but many cases seem to have slipped through the cracks. The two biggest diffs here are: - The `hello` example program was incorrectly talking about what was in the shader file (Slang no longer supports the "module" or "pipeline" constructs from Spire), and so it wasn't just a simple rename. - The files under `tests/bindings` were mistakenly using `__SPIRE__` as a preprocessor guard, which means that they weren't actually testing what they meant to. Luckily, it looks like the relevant functionality didn't regress while these tests were unintentionally deactivated. 2017-11-08T02:43:39+00:00 Yong He yonghe@outlook.com 2017-11-08T02:43:39+00:00 urn:sha1:e1710807292544775dc6a0eb338af081fb94493e 2017-06-10T00:18:39+00:00 Tim Foley tfoley@nvidia.com 2017-06-10T00:18:39+00:00 urn:sha1:383bc767601b9503476e9664034dde26ba3c49c9 All of this is just related to cruft left over from the old project setup. 2017-06-10T00:10:47+00:00 Tim Foley tfoley@nvidia.com 2017-06-09T23:00:00+00:00 urn:sha1:44e3f612b832c45589c3efc5b416ff2604f26602 There were some dead project references lying around after the Spire->Slang rename, that don't affect builds from inside Visual Studio, but seem to break stand-alone build with `msbuild`. 2017-06-09T20:44:59+00:00 Tim Foley tfoley@nvidia.com 2017-06-09T18:34:21+00:00 urn:sha1:fcf83dbf9effab3bd98bad2b83b2468b7eb05cfd