[Windows] Fix VTK\QT and OpenCV discovery#618
[Windows] Fix VTK\QT and OpenCV discovery#618seanyen wants to merge 4 commits intointrolab:develfrom
Conversation
|
The old define of the opencv part of your version was indeed wrong, it has been updated in this commit: VTK could be included by PCL indirectly. DISABLE_VTK definition is from PCL definitions normally, if PCL has not been built with VTK. VTK is used in PCL for some filtering functions (like mesh decimation): rtabmap/corelib/src/util3d_surface.cpp Line 62 in bda18bc |
|
Can you show the cmake log status on your build? If PCL is not build with VTK, there should be a Not that DISABLE_VTK should not be set if PCL is built with VTK. |
|
@matlabbe I am using the PCL port (without |
|
I didn't try PCL 1.11.1 on Windows lately, but it seems it is built with VTK as there is no |
|
See also: #795 I think relying on the
However, PCL defines multiple more defines starting with |
|
Didn't notice before, but you should make pull request on master branch, devel is pretty old. That should fix OpenCV SIFt problem. For DISABLE_VTK, see this pull request instead: #871 |
This pull request is to fix the case where it is building with
WITH_QT=OFF(which wouldn't find VTK consequently) and OpenCV w/oNONFREEmodule built (tested with OpenCV4.3).