Work around hardcoded slangc path in slangpy tests (#9563)

see shader-slang/slangpy#696

Also copy libslang.so in a more robust way to cope with slangpy version
bumps

Author: expipiplus1

.github/actions/common-test-setup/action.yml

@@ -60,11 +60,12 @@ runs:
           # On Windows, DLLs should be in the same directory as executables or in PATH
           # Use $GITHUB_PATH instead of $PATH for preservation across steps and
           # avoid unix-like/windows-like path issues
-          # echo "$bin_dir" >> $GITHUB_PATH
-          # echo "$lib_dir" >> $GITHUB_PATH
-          echo "skipping setting PATH in Windows"
+          :
         fi
 
+        # Make slangc available
+        echo "$bin_dir" >> $GITHUB_PATH
+
         # List directory contents
         echo "Contents of bin_dir ($bin_dir):"
         ls -a "$bin_dir" 2>/dev/null || echo "bin_dir not found"

.github/workflows/ci-slang-test-container.yml

@@ -269,6 +269,25 @@ jobs:
           echo "bin_dir location: $bin_dir"
           echo "lib_dir location: $lib_dir"
 
+          #
+          # THIS IS A HUGE HACK, the latest slangpy release hardcoded this
+          # directory when looking for slangc. We should remove the offending
+          # code from slangpy and just put slangc into PATH here. The offending
+          # code is find_slangc() in
+          # slangpy/tests/device/test_precompiled_modules.py
+          #
+          # See https://github.com/shader-slang/slangpy/issues/696
+          #
+          SLANGC_TARGET_DIR="$SITE_PACKAGES/build/pip/_deps/slang-src/bin"
+          mkdir -p "$SLANGC_TARGET_DIR"
+          # Copy slangc binary to the expected location
+          if [[ "${{ inputs.os }}" == "windows" ]]; then
+              cp -v "$bin_dir/slangc.exe" "$SLANGC_TARGET_DIR/"
+          else
+              cp -v "$bin_dir/slangc" "$SLANGC_TARGET_DIR/"
+              chmod +x "$SLANGC_TARGET_DIR/slangc"
+          fi
+
           # Remove old slang libraries and copy new ones
           echo "Removing old slang libraries..."
           rm -f "$SITE_PACKAGES/slangpy"/libslang*
@@ -278,7 +297,7 @@ jobs:
 
           # Create symlink for the old library version that slangpy extension was linked against
           echo "Creating symlink for slangpy compatibility..."
-          ln -sf libslang-compiler.so "$SITE_PACKAGES/slangpy/libslang-compiler.so.0.2025.21.2"
+          ln -sf libslang-compiler.so "$SITE_PACKAGES/slangpy/libslang-compiler.so.0.2025.24.3"
 
           echo "Listing files in slangpy directory..."
           ls -la "$SITE_PACKAGES/slangpy/"

.github/workflows/ci-slang-test.yml

@@ -214,10 +214,31 @@ jobs:
           echo "Site packages directory: $SITE_PACKAGES"
           echo "bin_dir location: $bin_dir"
           echo "lib_dir location: $lib_dir"
+
+          #
+          # THIS IS A HUGE HACK, the latest slangpy release hardcoded this
+          # directory when looking for slangc. We should remove the offending
+          # code from slangpy and just put slangc into PATH here. The offending
+          # code is find_slangc() in
+          # slangpy/tests/device/test_precompiled_modules.py
+          #
+          # See https://github.com/shader-slang/slangpy/issues/696
+          #
+          SLANGC_TARGET_DIR="$SITE_PACKAGES/build/pip/_deps/slang-src/bin"
+          mkdir -p "$SLANGC_TARGET_DIR"
+          # Copy slangc binary to the expected location
+          if [[ "${{ inputs.os }}" == "windows" ]]; then
+              cp -v "$bin_dir/slangc.exe" "$SLANGC_TARGET_DIR/"
+          else
+              cp -v "$bin_dir/slangc" "$SLANGC_TARGET_DIR/"
+              chmod +x "$SLANGC_TARGET_DIR/slangc"
+          fi
+
           # Copy library files
           if [[ "${{ inputs.os }}" == "windows" ]]; then
-            cp "$bin_dir"/slang*.dll "$SITE_PACKAGES/slangpy/" || { echo "Failed to copy library files"; exit 1; }
+            cp -v "$bin_dir"/slang*.dll "$SITE_PACKAGES/slangpy/" || { echo "Failed to copy library files"; exit 1; }
           else
+
             # This is kind of awkward because the version numbers might be
             # different between the old libslang-compiler and the new one, so
             # we need to make sure we overwrite the old one. This logic also