Christoph Lipka
Christoph Lipka
**Summary** On a GitHub Workflows runner I'm seeing configure failing to find ImfInputReadPixels in -lIlmImf, and therefore being unable to enable OpenEXR support during the build. **POV-Ray Version** - Incarnation:...
We should have a script that we can run on the "raw" source package to create a Unix-specific distribution package; such a package should have the following features: - does...
We need to review, and possibly update, the list of contributors in our source code.
Unless `#version 3.8` is specified, any v3.8 features should either be disabled (if automatic) or trigger a warning (if requiring extra syntax), so that the user doesn't accidently mark a...
The following sample, include or similar files need overhauling: **Missing licensing information:** - [ ] (none identified yet) **Renders with warnings, and/or does not start with a `#version` directive:** -...
According to the documentation, as of v3.7 the benchmark should run without having to actually install POV-Ray, and with just the executable binary present. This is actually not the case...
Setting the options `+kfi4 +kff4 +sf3 +ef5` will currently cause frames 4 and 5 to be rendered.
We should investigate using the `-Bsymbolic` and `-fno-semantic-interposition` compiler switches in our Unix build process to try and improve performance, as suggested here: https://old.reddit.com/r/programming/comments/ny7wk6/
When started from an INI file that has obsolete settings (e.g. `Histogram_Name=Foo`), and a parse error occurs in the scene file, POV-Ray for Windows jumps to the location of the...