OSL script comilation fails #78065

New Issue

System Information
Operating system: Darwin-19.5.0-x86_64-i386-64bit 64 Bits
Graphics card: AMD Radeon Pro 555 OpenGL Engine ATI Technologies Inc. 4.1 ATI-3.9.15

Blender Version
Broken: version: 2.83.0, branch: master, commit date: 2020-06-03 14:38, hash: 211b6c29f7
Worked: (newest version of Blender that worked as expected)

Short description of error
OSL script compilation fails, Also when using the Blender documentation example

https://docs.blender.org/manual/en/latest/render/shader_nodes/osl.html#script-node

Exact steps for others to reproduce the error
See if OSL works on your mac.

BlenderTest.osl

**System Information** Operating system: Darwin-19.5.0-x86_64-i386-64bit 64 Bits Graphics card: AMD Radeon Pro 555 OpenGL Engine ATI Technologies Inc. 4.1 ATI-3.9.15 **Blender Version** Broken: version: 2.83.0, branch: master, commit date: 2020-06-03 14:38, hash: `211b6c29f7` Worked: (newest version of Blender that worked as expected) **Short description of error** OSL script compilation fails, Also when using the Blender documentation example https://docs.blender.org/manual/en/latest/render/shader_nodes/osl.html#script-node **Exact steps for others to reproduce the error** See if OSL works on your mac. [BlenderTest.osl](https://archive.blender.org/developer/F8633579/BlenderTest.osl) ![Screen Shot 2020-06-20 at 1.21.46 PM.png](https://archive.blender.org/developer/F8633580/Screen_Shot_2020-06-20_at_1.21.46_PM.png)

Added subscriber: @Hemdrup

Added subscriber: @Josephbburg

That isn't the console. On MacOS you have to start Blender from a terminal window to see the console prints. Only Windows opens from a console by default. You should use a terminal anyways-- you can't have multiple instances otherwise (well, on a Mac).

This probably isn't a bug, but if the OSL documentation example fails to compile, that is a problem that is worth fixing.

That isn't the console. On MacOS you have to start Blender from a terminal window to see the console prints. Only Windows opens from a console by default. You should use a terminal anyways-- you can't have multiple instances otherwise (well, on a Mac). This probably isn't a bug, but if the OSL documentation example fails to compile, *that* is a problem that is worth fixing.

Added subscriber: @Joseph

@Joseph Brandenburg (TheAngerSpecialist)

Opened Blender with the terminal. The terminal says;

ERROR: /Applications/Blender.app/Contents/Resources/2.83/scripts/addons/cycles/shader/stdcycles.h:31: error: error: could not find include file: stdosl.h

@Joseph Brandenburg (TheAngerSpecialist) Opened Blender with the terminal. The terminal says; ERROR: /Applications/Blender.app/Contents/Resources/2.83/scripts/addons/cycles/shader/stdcycles.h:31: error: error: could not find include file: stdosl.h ![Screen Shot 2020-06-22 at 3.55.20 PM.png](https://archive.blender.org/developer/F8636968/Screen_Shot_2020-06-22_at_3.55.20_PM.png)

Odd, If I'm not mistaken, that is what Cycles says when it has not been built with OSL support. Did you build Blender or download it?

I suppose this sort of thing may also happen if a package is not found on the system, but I don't know if that's true in Mac like it is in the Linux world. I doubt Blender would rely on system packages like that on a Mac... Even on Linux, Blender is available as a snap package.

Odd, If I'm not mistaken, that is what Cycles says when it has not been built with OSL support. Did you build Blender or download it? I suppose this sort of thing may also happen if a package is not found on the system, but I don't know if that's true in Mac like it is in the Linux world. I doubt Blender would rely on system packages like that on a Mac... Even on Linux, Blender is available as a snap package.

Added subscriber: @iss

I had no problem compiling this shader on windows. Can't check on mac really

@Joseph Brandenburg (TheAngerSpecialist)

I download Blender and then drag it into the application folder to replace the previous version of Blender in the Application folder.

No expert on how the Mac apps work. But, this is how I understand it.
Each application is like an app on Mac with all its content inside like a folder, why the drag and drop works, and why there is no uninstall or install on Mac. Just drag and drop.

@Joseph Brandenburg (TheAngerSpecialist) I download Blender and then drag it into the application folder to replace the previous version of Blender in the Application folder. No expert on how the Mac apps work. But, this is how I understand it. Each application is like an app on Mac with all its content inside like a folder, why the drag and drop works, and why there is no uninstall or install on Mac. Just drag and drop.

Added subscriber: @vitorbalbio-3

Added subscriber: @IPv6

Have same problem on Mac... OSL shaders are not compilable anymore

I have the same problem in MacOs (Catalina 10.15.16). Compilation of any OLS-script is failed with error message "Unable to find stdosl.h". The problem exists in current official release 2.83.4 and an latest 2.91
This OSL files was perfectly compilable on same machine in 2.82a (!)

i managed to workaround problem, may be this can help:

I checked content of "/scripts/addons/cycles/shader/" folders and there is no stdosl.h, see screenshots -

But the file present in same path in 2.82a, see screenshots -

after copying stdosl.h, oslutil.h, vector2.h, vector4.h from 2.82 into 2.83 on same location - OSL shaders started to compile without errors
So probably dmg bundling miss some OSL-related files... with missing files compilation works as expected

I have the same problem in MacOs (Catalina 10.15.16). Compilation of any OLS-script is failed with error message "Unable to find stdosl.h". The problem exists in current official release 2.83.4 and an latest 2.91 This OSL files was perfectly compilable on same machine in 2.82a (!) i managed to workaround problem, may be this can help: I checked content of "/scripts/addons/cycles/shader/" folders and there is no stdosl.h, see screenshots - ![Screenshot 2020-08-13 at 16.56.31.png](https://archive.blender.org/developer/F8777267/Screenshot_2020-08-13_at_16.56.31.png) But the file present in same path in 2.82a, see screenshots - ![Screenshot 2020-08-13 at 16.59.26.png](https://archive.blender.org/developer/F8777269/Screenshot_2020-08-13_at_16.59.26.png) after copying stdosl.h, oslutil.h, vector2.h, vector4.h from 2.82 into 2.83 on same location - OSL shaders started to compile without errors So probably dmg bundling miss some OSL-related files... with missing files compilation works as expected

Removed subscriber: @Joseph

This issue was referenced by 421ce37f9c

This issue was referenced by 421ce37f9c16e8489814eb3ce6bb03b7cf64aeef

This issue was referenced by c5519d4b6f

This issue was referenced by c5519d4b6f7f83bd8dab8491b8615512b65686ac

Changed status from 'Needs Triage' to: 'Resolved'

Download

What's New

Blender Studio

Manual

Developers Blog

Documentation

Benchmark

Blender Conference

Development Fund

One-time Donations

OSL script comilation fails #78065