[vtk-developers] vtk-8.2.0-rc2 problem building wheels

[Jean-Christophe Fillion-Robin]

> VTK_ENABLE_VTKPYTHON:BOOL=OFF

As a side note, would it make sense to renamed this option to
VTK_BUILD_VTKPYTHON_EXECUTABLE (or VTK_ENABLE_VTKPYTHON_EXECUTABLE)

> distribution builds should try to enable *everything*


In that context, I don't think it makes sense to build VTK own python
interpreter. Ideally, it should be possible to run VTK test with or without
it.

I also envision we could have a "vtk-openvr" python module but it wouldn't
be available by default when installing vtk wheel. To support this level of
"modularity" , we would continue building part of VTK independently (for
example, we can already do this with the VTKOpenVR module)





On Thu, Dec 6, 2018 at 11:48 AM David E DeMarle <dave.demarle at kitware.com>
wrote:

> I think the dependency comes in for the sake of VTK's python tests, as
> those call vtkpython.
> Prabu can you try this and see if you get a pip worthy build out of it?
>
> https://gitlab.kitware.com/demarle/vtk/commits/WIP-break-wrappings-vtkpythoninterpreter-dependency
> Note you must set these two configure flags to get it to compile.
> BUILD_TESTING:BOOL=OFF
> VTK_ENABLE_VTKPYTHON:BOOL=OFF
> Longer term we should do a clean break by trying to move the bits of
> VTKPYTHON that remain in Wrapping/PythonCore to
> Utilities/PythonInterpretter and making sure the python tests agree.
>
> Regarding matplotlib, for the moment just leave it off in the wheels.
> Ben's point of wrapping everything and the corrolary that VTK's modules
> should be atomic (options don't change the library internals) is an
> important goal that we won't fix in 8.2. We made strides in VTK 6.0 and
> will get much closer in 9.0, hopefully packagers and all consumers of VTK
> will have a better time of it after 9.
>
> David E DeMarle
> Kitware, Inc.
> Principal Engineer
> 21 Corporate Drive
> Clifton Park, NY 12065-8662
> Phone: 518-881-4909
>
>
>
> On Wed, Nov 28, 2018 at 3:44 PM Ben Boeckel via vtk-developers <
> vtk-developers at public.kitware.com> wrote:
>
>> On Wed, Nov 28, 2018 at 15:06:43 -0500, Prabhu Ramachandran wrote:
>> > Does vtkWrappingPythonCore depend on vtkPythonInterpreter?
>> > vtkWrappingPythonCore does not link to libpython or to
>> vtkPythonInterpreter.
>>
>> My bad, it's a COMPILE_DEPENDS. Though why that is isn't obvious.
>> Removing that dependency and then disabling the module should work.
>>
>> > The wheels by default do not seem to enable vtkRenderingMatplotlib
>> although I am
>> > not sure if it should be added by default in the future, in which case
>> this is a
>> > more serious issue.
>>
>> IMO, distribution builds should try to enable *everything* so there
>> isn't a question of "what do I have today?" when doing `import vtk`.
>> Keeping it disabled for 8.2 sounds fine, but 9.x will make it easier to
>> not have the linking problem.
>>
>> --Ben
>> _______________________________________________
>> Powered by www.kitware.com
>>
>> Visit other Kitware open-source projects at
>> http://www.kitware.com/opensource/opensource.html
>>
>> Search the list archives at: http://markmail.org/search/?q=vtk-developers
>>
>> Follow this link to subscribe/unsubscribe:
>> https://public.kitware.com/mailman/listinfo/vtk-developers
>>
>>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://public.kitware.com/pipermail/vtk-developers/attachments/20181207/ddd092b4/attachment.html>