Modules caching issues #7650
Unanswered
daniilvinn
asked this question in
Q&A
Replies: 1 comment
-
When you serialize a module, you're serializing the entire translation unit (including all __included files). Files pulled in via __include are part of the same module and don't need separate serialization. Modules that are imported however are separate modules and need to be handled independently. You might find docs/user-guide/04-modules-and-access-control.md and docs/user-guide/08-compiling.md useful :) If you think that slang isn't finding a slang-module file in the search path when it should are you able to share a reproducer please I hope this helps |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Hello everyone. I am having issues with caching Slang shaders and using precompiled code.
I am using the newest Slang release and built-in
serialize
/loadModuleFromIRBlob()
API. However, I can't get some things right.All of my slang shaders are defined in the modules. Some modules are built from multiple files (via
implementing
+__include
). Files with entry points declare a module as well.Note that I 100% have provided correct search paths for compiler, so it can find those modules.
The questions are:
#2
is yes, then do I also need to serialize__include 'my/path'
separately, or only "top file" that includes all those files via__include
?Right now I am facing issues that depend on the setup I have:
Thanks for help.
Beta Was this translation helpful? Give feedback.
All reactions