[vtk-developers] VTK Python & BUILD_SHARED_LIBS=OFF

Burlen Loring burlen.loring at gmail.com
Thu Sep 13 15:09:06 EDT 2018


Cool, thanks for all the info

sounds like this will be supported in the near future. I'd like to try 
it out. What is the eta? What's the best way to follow progress?

On 09/11/2018 01:16 PM, Ben Boeckel wrote:
> On Sun, Sep 09, 2018 at 08:36:18 -0400, Utkarsh Ayachit wrote:
>> You're correct an all accounts. That's indeed an issue. I am not sure
>> what's the best way: should we install the header and export the
>> libraries, or create a new library/api that dependent projects can
>> call to init the static Python modules or something even more
>> creative. If we go the truly modular route, CMakeLoadAllPythonModules
>> is an anathema. It inits all modules that VTK was built with and not
>> the only the modules that the app depends on. Ideally, it'd be the
>> latter. Not sure how we could do that. Ben/David, any ideas?
> Yes. When rewriting the Python wrapping function for the new module
> system, the static Python libraries have generated headers installed for
> initializing the installed static modules.
>
> It also generates a header for initializing "all" modules with a
> function name that can be specified. This is how the static `vtkpython`
> works in the new module system.
>
> It certainly requires removing the PythonD libraries though (the new
> module system has its version of that topic in its history).
>
> --Ben



More information about the vtk-developers mailing list