[Vulkan] Fix Ninja build failure by removing wildcard dependencies

[Peddinti-Sriram-Bharadwaj]

Summary

Fixes Ninja build support for the Vulkan backend by removing wildcard usage in DEPENDS.

Fixes #16354
Fixes #14984

The backends/vulkan/cmake/ShaderLibrary.cmake file previously used a wildcard (${shaders_path}/*) in the DEPENDS clause of a custom command. Ninja does not support wildcard expansion in dependencies, which caused the build to fail with:
ninja: error: '.../glsl/*', needed by 'vk_compute_shaders/spv.cpp', missing and no known rule to make it.

This PR replaces the wildcard usage with an explicit file(GLOB ...) command to resolve the source files before passing them to DEPENDS, making the build compatible with the Ninja generator.

Test plan

Verified the fix by rebuilding the Android executor_runner using Ninja:

1. Clean Build: rm -rf cmake-out-android
2. Configure:

   cmake . -G Ninja -DCMAKE_INSTALL_PREFIX=cmake-out-android \
     -DCMAKE_TOOLCHAIN_FILE=$ANDROID_NDK/build/cmake/android.toolchain.cmake \
     -DANDROID_ABI=arm64-v8a \
     -DANDROID_PLATFORM=android-26 \
     -DEXECUTORCH_BUILD_VULKAN=ON \
     -DEXECUTORCH_BUILD_EXTENSION_DATA_LOADER=ON \
     -DEXECUTORCH_BUILD_EXTENSION_MODULE=ON \
     -DEXECUTORCH_BUILD_EXTENSION_TENSOR=ON \
     -DEXECUTORCH_BUILD_EXTENSION_NAMED_DATA_MAP=ON \
     -DEXECUTORCH_BUILD_EXTENSION_LLM=OFF \
     -DPYTHON_EXECUTABLE=$(which python) \
     -Bcmake-out-android

3. Build: ninja -C cmake-out-android -> Success (previously failed).
4. Runtime Verification: Pushed the built executor_runner to an Android device and executed a MobileNetV2 model to ensure the binary loads and runs (confirmed same runtime behavior as the Make build).

cc @SS-JIA @manuelcandales @digantdesai @cbilgin

[pytorch-bot]

🔗 Helpful Links

🧪 See artifacts and rendered test results at hud.pytorch.org/pr/pytorch/executorch/16394

• 📄 Preview Python docs built from this PR

Note: Links to docs will display an error until the docs builds have been completed.

❗ 1 Active SEVs

There are 1 currently active SEVs. If your PR is affected, please view them below:

• B200 runners are down due to network issues

✅ No Failures

As of commit e8606eb with merge base c730feb ():
💚 Looks good so far! There are no failures yet. 💚

This comment was automatically generated by Dr. CI and updates every 15 minutes.

[meta-cla]

Hi @Peddinti-Sriram-Bharadwaj!

Thank you for your pull request and welcome to our community.

Action Required

In order to merge any pull request (code, docs, etc.), we require contributors to sign our Contributor License Agreement, and we don't seem to have one on file for you.

Process

In order for us to review and merge your suggested changes, please sign at https://code.facebook.com/cla. If you are contributing on behalf of someone else (eg your employer), the individual CLA may not be sufficient and your employer may need to sign the corporate CLA.

Once the CLA is signed, our tooling will perform checks and validations. Afterwards, the pull request will be tagged with CLA signed. The tagging process may take up to 1 hour after signing. Please give it that time before contacting us about it.

If you have received this in error or have any questions, please contact us at cla@meta.com. Thanks!

[meta-cla]

Thank you for signing our Contributor License Agreement. We can now accept your code for this (and any) Meta Open Source project. Thanks!

[Peddinti-Sriram-Bharadwaj]

@pytorchbot label "release notes: build"

[Peddinti-Sriram-Bharadwaj]

@pytorchbot label "release notes: vulkan"

[mergennachin]

This is not equivalent to the previous behavior.

What about other file extensions?

  file(GLOB VULKAN_SHADERS
      "${shaders_path}/*.glsl"
      "${shaders_path}/*.glslh"
      "${shaders_path}/*.yaml"
      "${shaders_path}/*.h"
  )

Changes to .yaml, .glslh, or .h files will not trigger a rebuild.

[Peddinti-Sriram-Bharadwaj]

@mergennachin thank you the feedback, I shall make a more exhaustive glob that takes into account these file extensions as well?
please let me know any other changes I have to make, I will put them together and submit a new pr.

[mergennachin]

I shall make a more exhaustive glob that takes into account these file extensions as well?

Yes exactly.

please let me know any other changes I have to make, I will put them together and submit a new pr.

you can just update this PR directly, no need to create another PR.

[Peddinti-Sriram-Bharadwaj]

@mergennachin I have updated the PR, please check.

[mergennachin]

@Peddinti-Sriram-Bharadwaj I don't see the change -- where is it?

[Peddinti-Sriram-Bharadwaj]

@Peddinti-Sriram-Bharadwaj I don't see the change -- where is it?

im sorry i thought i had commited changes to the main branch, but it was to my fix branch. now its updated for sure.