Okay, I got it. On first tracking, I have thought this would have something to ABI.
But I thought it’s not simple for ABI. So, I just tried to find the clue in more simple case, I just had insterested in that definite same codes work each differently on simple console app and Unreal with the same VTK shared libs. In both, they run with a loading VTK shared library at start up instead of way using dlopen.
I don’t think this have a something with RTTI.
Do you think there is wrong for shared library?
a) symbols for static variables that aren’t resolved correctly?
I don’t use static variables for VTK. At sample codes use variables on stack and heap.
b) symbols for template instantiations that aren’t resolved correctly
I think it would be very rare because simple console app works correctly for same codes which use VTK template array API.
c) static initialization of translation units not occurring in the correct order
I’m not sure but I don’t have a lot idea about this.
When do this things go? what does it going to be related with Shared Library?