Thanks for the pointer - beating myself up now because I didn’t think of checking the available options earlier (I do have
VTK_MODULE_ENABLE_VTK_RenderingContextOpenGL2 as setting shown in cmake, it wasn’t enabled yet)! Unfortunately, this also didn’t help yet, our code still crashes at vtkContext2D::GetDevice returning a nullptr… so I guess I might miss yet another module?
Here’s the list of VTK components which I currently pass into autoinit (several of course are probably only needed for unrelated purposes):
I’m not familiar with the internals of VTK’s module system, so in the following I’m probably missing loads of intricate stuff; I just can say that from a user’s perspective, I do find this behavior of having functionality that compiles fine, but then crashes at runtime quite annoying; my gut tells me there should be a better way - VTK telling you what modules to auto-configure (or even automatically doing that), or at least telling me on startup of the specific functionality, that currently no implementation of this functionality is available (and ideally the names of the modules which can provide it). I guess if this could be done easily, it would have been done already. I hope this could be done at some point in the future, I would find it extremely helpful!
Or is there at least a list of modules and for what they are required? I’ve skimmed the VTK Module System description, but for me as a user I don’t see any actionable information in there regarding my issue - i.e. information on which modules I need to autoinit for specific functionality to work.