New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
oslc un-escapes the path to stdosl.h #866
Comments
Hi, sorry for this to slip through the cracks. Can somebody verify whether or not this is still a problem in the current master and/or release branch? |
#1073 seems to be on a related topic, but I'm not sure if it addresses this particular bug. |
Not a problem! Between the time of reporting and now I'm only aware of a single blender user bumping into this one. I can still reproduce the issue
Update: applying #1073 did not seem to help |
So the problem is specifically when the path to oslc contains a directory starting with n? Or is it also a problem when the osl file is in a directory starting with n? um, I mean,
Both problems, just first, or just second? |
Only the first, |
Proposed fix in #1101. Would you by any chance be able to test this on Windows? |
That worked, with a minor caveat, i build against an rather old version oiio (1.8.13) which seems to be missing |
Closing, should be fixed by #1101. It's in master now, and I will backport to 1.10, pending tests. |
OSL 1.10.9 fixes osl-bug 866 [1] which is long standing issue on windows where paths get un-escaped and osl breaks when you install it to for instance c:\blender-tests\new-boolean This patch bumps osl to 1.10.9, and since osl is llvm's only consumer, llvm/clang were bumped 9.0.1 Removed some of the patches that were no longer needed Builds and passes all tests on windows and linux [1] AcademySoftwareFoundation/OpenShadingLanguage#866 Differential Revision: https://developer.blender.org/D6744 Reviewers: brecht
Problem
When installing oslc in a path that has \n in it ( such as c:\osl_test\new\ ) oslc will
fail trying to compile any shader. due to the path being un-escaped somewhere.
Steps to Reproduce
I validated with procmon that the path is indeed unescaped
Versions
The text was updated successfully, but these errors were encountered: