Jefferson Amstutz

Thanks, this is definitely a nice start: that's a very common setup, where I was curious if you were running on an old KNL machine. :) I'll ping @Twinklebear here...

Hi, Could you verify that the bug still remains in the current `devel` branch? If it does, we can look into a good test case to reproduce, as we haven't...

Hi, Yes, you've definitely found quite a soft spot in our releases. Some of the history here: we used to have N different example applications all showcasing subsets of functionality...

Hmmm, interesting setup. I don't know anything about colab.research.google.com, but it looks very Python heavy (as is Jupyter?). We contribute regularly to VTK to make sure that OSPRay's capabilities are...

We discussed this in our weekly team meeting yesterday, and the leading candidate is to employ SWIG to give us several targets for OSPRay API bindings (which includes Python!). We...

Yes, we have discussed expanding `ospLoadModule()` (which is what does the ispc module load in `ospInit()`) to allow for a prefix path. However, on Unix platforms you can use `LD_LIBRARY_PATH`...

Just curious (maybe a question for @demarle?): did this ever work before in your macOS builds, or is this a new problem?

This is fixed in the `v1.8.4` release, via PR #312.

All of those are good suggestions, and we can implement them in `v2.0` (especially the STATIC build). We would likely keep modules them as SHARED libraries, as we want to...

Thanks for the bug report! Is there a because we use CMake the project should already be buildable with MINGW -- what kind of error are you seeing when you...