OpenShadingLanguage
OpenShadingLanguage copied to clipboard
Advanced shading language for production GI renderers
Update osltoyrenderer.cpp: auto-detect output variable -- doesn't need to be Cout if there's only on
auto-detect output variable -- doesn't need to be Cout if there's only one ## Description ## Tests ## Checklist: - [ ] I have read the [contribution guidelines](../CONTRIBUTING.md). - [...
# Master list of `osltoy` feature requests `osltoy` is a small example program loosely inspired by [shadertoy](https://www.shadertoy.com/) -- a Qt application that lets you load or type in an OSL...
### Problem OSL builds currently generate the Bison parser code during their builds. It would be really great if someone could pre-generate these files and include them in the repo...
## Description Updates the osltoy application to use 4 spaces in the editor window instead of tab characters. ## Tests I'm not sure that this change warrants a test case,...
### Problem **Actual behavior:** FAILED: src/liboslexec/CMakeFiles/oslexec.dir/shadingsys.cpp.o /usr/lib/llvm14/bin/clang++ -DCUDA_TARGET_ARCH=\"sm_60\" -DOIIO_DISABLE_DEPRECATED=900000 -DOIIO_HIDE_FORMAT=1 -DOSL_CUDA_VERSION=\"\" -DOSL_EXPORTS -DOSL_FAST_MATH=1 -DOSL_INTERNAL=1 -DOSL_LLVM_FULL_VERSION=\"14.0.6\" -DOSL_LLVM_VERSION=140 -DOSL_OPTIX_VERSION=\"\" -D__STDC_CONSTANT_MACROS -D__STDC_LIMIT_MACROS -Doslexec_EXPORTS -Doslparse=OSL_v1_14_1_oslparse -Dosoparse=OSL_v1_14_1_osoparse -I./OpenShadingLanguage/build/include -I./OpenShadingLanguage/build/src/include -I./OpenShadingLanguage/src/include -I./OpenShadingLanguage/ext/dist/include -I./OpenShadingLanguage/src/liboslexec -I./OpenShadingLanguage/src/liboslcomp -isystem /usr/lib/llvm14/include...
# Master list of `testrender` feature requests We will use this issue to collect individual suggestions or feature requests for `testrender`. Some are larger projects that can be later forked...
Our CI doesn't actually build and test on Windows. This causes no end of despair. How hard can it be? You don't really need to know anything about OSL internals...
StepSecurity automatically generates a pull request that adds several hardening measures to your repo. Run it [here](https://app.stepsecurity.io/securerepo). By default, the process will create one composite PR that makes multiple changes....
The OpenSSF Best Practices Badge suggests [signing release artifacts](https://www.bestpractices.dev/en/criteria). Consider using OpenEXR's [release-sign.yml](https://github.com/AcademySoftwareFoundation/openexr/blob/main/.github/workflows/release-sign.yml) workflow as a template. It's triggered on release creation and does these steps: 1. Runs `get archive`...
The OpenSSF Best Practices Badge suggests [signing release tags](https://www.bestpractices.dev/en/criteria). The process is simple, described [here](https://docs.github.com/en/authentication/managing-commit-signature-verification/signing-tags): simply create the release from a tag created with `-s`: `$ git tag -s v1.2.3`...