New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Build with vtk89 #1312
Build with vtk89 #1312
Conversation
Tried to update renamed CMake options.
…90.lib It was a recent regression in VTK. Fixed by updating to latest VTK.
Does python37.dll exist? Do you see more information if you start from the debugger? Do you see any additional information in Windows event log? |
Slicer is expected to link against python36. See https://github.com/Slicer/Slicer/blob/ba6e736fba521d4a5d653af03b204add643f793a/SuperBuild/External_python.cmake#L60 @cpinter During the project week, did we find out the root cause of this ? |
Looks like the changes requiring |
1 similar comment
Looks like the changes requiring |
Let me know if/when you'd like me to try a mac build. |
Sorry for the delay... I'm back now. @jcfr Have you had time to check on your other laptop regarding passing the |
Sadly, I can't find the changes on my laptop. |
Thanks for the info, @jcfr! If anyone has an idea about how to address any of the three issues (1. wrong VTK version in ifdef, 2. wrong python wrapping of VTK class, 3. python37.dll issue), feel free to issue a new PR or just comment here. I'll work on other things now, but can test ideas using my build. |
You need to add:
|
Closing. This PR is superseded by Slicer/Slicer#5141 |
This branch is the continuation of the work of @lassoan in PR Slicer/Slicer#1252
Python wrapping of VTK classes seems to work. The remaining errors on Windows are:
The first error should not happen, as the precompiler directive of
#if VTK_MAJOR_VERSION >= 9 || (VTK_MAJOR_VERSION >= 8 && VTK_MINOR_VERSION >= 90)
should work (see line in question in generated file here). Maybe the VTK version variables are not propagated to the project. correctly
In the case of the second error, the python wrapping C++ file is quite different. In the current Slicer master, vtkImageGrowCutSegmentPython.cxx does not contain a PyvtkImageGrowCutSegment_vtkImageGrowCutSegment ragular constructor, but a VTK constructor PyvtkImageGrowCutSegment_NewInstance instead. It is possible that the class is not wrapped as a VTK class.