Skip to content

test: add example-tinyrender - #2180

Open
jinhgkim wants to merge 1 commit into
AcademySoftwareFoundation:mainfrom
jinhgkim:example-tinyrender
Open

jinhgkim wants to merge 1 commit into
AcademySoftwareFoundation:mainfrom
jinhgkim:example-tinyrender

Conversation

@jinhgkim

@jinhgkim jinhgkim commented Oct 5, 2026

Copy link
Copy Markdown
Contributor

Closes #2175.

Add a minimal standalone renderer that is built against the installed OSL, as requested in #2175.

testrender and testshade are built as part of OSL, so they cannot notice a broken install. This test is a separate CMake project that uses find_package(OSL), compiles its shaders with the installed oslc, links OSL::oslexec, renders a small image, and compares it against a reference.

The renderer is the path tracer from "Ray Tracing in One Weekend" with its materials replaced by OSL shaders. Random numbers are reseeded per scanline so the image is the same for any number of threads.

Assisted-by: Claude Code / Opus-5.5

(Hold me closer, tiny render 🎵)

Checklist:

  • I have read the guidelines on contributions and code review procedures.
  • I have read the Policy on AI Coding Assistants
    and if I used AI coding assistants, I have an Assisted-by: TOOL / MODEL
    line in the pull request description above.
  • I have updated the documentation if my PR adds features or changes
    behavior.
  • I am sure that this PR's changes are tested in the testsuite.
  • I have run and passed the testsuite in CI before submitting the
    PR, by pushing the changes to my fork and seeing that the automated CI
    passed there. (Exceptions: If most tests pass and you can't figure out why
    the remaining ones fail, it's ok to submit the PR and ask for help. Or if
    any failures seem entirely unrelated to your change; sometimes things break
    on the GitHub runners.)
  • My code follows the prevailing code style of this project and I
    fixed any problems reported by the clang-format CI test.

@lgritz

lgritz commented Oct 7, 2026

Copy link
Copy Markdown
Collaborator

The Windows CI failure are something that's already been fixed, and if you rebase on the current main, it will go away.

Add a minimal standalone renderer that is built against the installed
OSL, as requested in AcademySoftwareFoundation#2175.

testrender and testshade are built as part of OSL, so they cannot
notice a broken install. This test is a separate CMake project that
uses find_package(OSL), compiles its shaders with the installed oslc,
links OSL::oslexec, renders a small image, and compares it against a
reference.

The renderer is the path tracer from "Ray Tracing in One Weekend" with
its materials replaced by OSL shaders. Random numbers are reseeded per
scanline so the image is the same for any number of threads.

Assisted-by: Claude Code / Opus-5.5
Signed-off-by: Jinnie Kim <jinhgkim@gmail.com>
@jinhgkim
jinhgkim force-pushed the example-tinyrender branch from b03c3fc to 234a2a8 Compare October 7, 2026 05:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Add example-tinyrender: a minimal standalone renderer test against the installed OSL

2 participants