-
Notifications
You must be signed in to change notification settings - Fork 83
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
Remove points #1534
Remove points #1534
Conversation
Needs Kitware/fletch#699 |
@mleotta Please review. How do I get a user name for Jenkins to see the issue with the linux build? |
jenkins test this please |
remove_occluded -> color_occluded remove_maked -> color_masked
@danlipsa this is failing because VTK 9.1 is not the default on the CI machines. Either I need to get consensus to make it the default or we need to conditionally disable these new features if building with older VTK. |
I see. Yes, the filter I use is not available for VTK < 9.1 |
It seems that we need to update this file: The alternative is to find away to disable the new features you added when using older VTK or to use an alternate implementation that does not need VTK 9.1. |
@mleotta Are the CIs updated? |
jenkins test this please |
@mleotta So now I compile color_mesh only if we have VTK >= 9.1. This way we keep visgui working for older versions of VTK. Would that work? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
See inline comments.
I think disabling color-mesh for older VTK is a reasonable compromise. Disabling only the use of vtkRemovePolyData
within color-mesh would be better, but also a lot messier.
Jenkins test this please |
All the build failures say 'Build step 'Execute shell' marked build as failure' at the very end despite the build succeeding and the tests passing. |
Jenkins test this please |
@mleotta Tests passed so I assume we are ok to merge? |
No description provided.