<feed xmlns='http://www.w3.org/2005/Atom'>
<title>slang.git/cmake/SlangConfig.cmake.in, branch master</title>
<subtitle>Making it easier to work with shaders</subtitle>
<id>https://git.yummers.dev/slang.git/atom?h=master</id>
<link rel='self' href='https://git.yummers.dev/slang.git/atom?h=master'/>
<link rel='alternate' type='text/html' href='https://git.yummers.dev/slang.git/'/>
<updated>2025-08-21T17:41:24+00:00</updated>
<entry>
<title>Fix SLANGC_EXECUTABLE search path in slangConfig.cmake (#8200)</title>
<updated>2025-08-21T17:41:24+00:00</updated>
<author>
<name>Sergei Kachkov</name>
<email>kachkov98@gmail.com</email>
</author>
<published>2025-08-21T17:41:24+00:00</published>
<link rel='alternate' type='text/html' href='https://git.yummers.dev/slang.git/commit/?id=44815ba48c1d149137a2210ca3fccfe3bda2626e'/>
<id>urn:sha1:44815ba48c1d149137a2210ca3fccfe3bda2626e</id>
<content type='text'>
This patch changes the order of searching slangc executable. This bug
affects the following scenario: let's assume that user has a binary
release of slang package and wants to use it via `find_package(slang
CONFIG HINTS &lt;path to binary release&gt;)`, but there is also an
environment variable that points to some other slang release (e.g. user
has Vulkan SDK in the `$PATH`). In that case, find_package will
successfully find a desired slang package, but find_program in
slangConfig.cmake will check environment variable first, and in the
result SLANGC_EXECUTABLE will point to slangc from Vulkan SDK and not
from the downloaded package.

Co-authored-by: Ellie Hermaszewska &lt;ellieh@nvidia.com&gt;</content>
</entry>
<entry>
<title>Add SlangConfig.cmake with slang build targets (#5674)</title>
<updated>2024-12-03T17:50:11+00:00</updated>
<author>
<name>ov-l</name>
<email>186710607+ov-l@users.noreply.github.com</email>
</author>
<published>2024-12-03T17:50:11+00:00</published>
<link rel='alternate' type='text/html' href='https://git.yummers.dev/slang.git/commit/?id=5d8cf475b352ab517c565ccee59461640da63a2a'/>
<id>urn:sha1:5d8cf475b352ab517c565ccee59461640da63a2a</id>
<content type='text'>
* Modify package config

* Apply formatting.

* Make sure build works for Emscripten

* Add documentation on install target.

---------

Co-authored-by: obhi-d &lt;obi.de.online@gmail.com&gt;</content>
</entry>
</feed>
