Circular dep build issue with opencascade

Looks like a OCCT issue to me.

In any case, you probably need to build first occt without VTK, then VTK against OCCT, then OCCT again against VTK.

I guess I figured that VTK might need to somehow change the name of TKernel target for its own use so that it doesn't conflict with opencascade. But maybe opencascade needs to not include it from VTK? It's all way beyond my cmake fu.

There is a discussion at opencascade here https://dev.opencascade.org/content/build-failed-vtk-addlibrary-cannot-create-target-tkernel-because-imported-target-same-name but not much determined yet.

FYI - https://github.com/Open-Cascade-SAS/OCCT/issues/387

So I think the problem is that OCCT is importing too many components from VTK. If I make this change:

diff --git a/adm/cmake/vtk.cmake b/adm/cmake/vtk.cmake
index 48650fe7df..8f284b97aa 100644
--- a/adm/cmake/vtk.cmake
+++ b/adm/cmake/vtk.cmake
@@ -2,7 +2,7 @@

 # vcpkg processing
 if (BUILD_USE_VCPKG)
-  find_package(VTK REQUIRED)
+  find_package(VTK REQUIRED COMPONENTS CommonCore)
   set(CSF_VTK VTK::CommonCore)
   set(IS_VTK_9XX 1)
   if (WIN32)
@@ -74,7 +74,7 @@ if (3RDPARTY_VTK_DIR AND EXISTS "${3RDPARTY_VTK_DIR}")
   set (ENV{VTK_DIR} "${3RDPARTY_VTK_DIR}")
 endif()

-find_package(VTK QUIET)
+find_package(VTK COMPONENTS CommonCore QUIET)

 if (3RDPARTY_VTK_DIR AND EXISTS "${3RDPARTY_VTK_DIR}")
   set (ENV{VTK_DIR} ${CACHED_VTK_DIR})

Then I don't get the initial import error. But then I get:

VTK version (9.3.1)
-- Info: The directories of 3rdparty headers: 
	/usr/include
	/usr/include/freetype2
-- Info: The directories of 3rdparty libraries: 
	/usr/lib64
-- 
Info: (00:00:00) Start collecting all OCCT header files into /builddir/build/BUILD/opencascade-7.9.0-build/occt-V7_9_0/redhat-linux-build/inc ...
-- Info: (00:00:00) End the collecting
-- Info: Used native memory manager
-- Info: (00:00:00) OCCT toolkits processed
-- Info: (00:00:00) OCCT configuration files prepared
-- Configuring done (2.1s)
CMake Error at /usr/lib64/cmake/vtk/VTK-targets.cmake:674 (set_target_properties):
  The link interface of target "VTK::RenderingUI" contains:

    X11::X11

  but the target was not found.  Possible reasons include:

    * There is a typo in the target name.
    * A find_package call is missing for an IMPORTED target.
    * An ALIAS target is missing.

Call Stack (most recent call first):
  /usr/lib64/cmake/vtk/vtk-config.cmake:145 (include)
  adm/cmake/vtk.cmake:77 (find_package)
  CMakeLists.txt:92 (include)
  CMakeLists.txt:919 (OCCT_INCLUDE_CMAKE_FILE)


CMake Error at /usr/lib64/cmake/vtk/VTK-targets.cmake:682 (set_target_properties):
  The link interface of target "VTK::glew" contains:

    GLEW::GLEW

  but the target was not found.  Possible reasons include:

    * There is a typo in the target name.
    * A find_package call is missing for an IMPORTED target.
    * An ALIAS target is missing.

Call Stack (most recent call first):
  /usr/lib64/cmake/vtk/vtk-config.cmake:145 (include)
  adm/cmake/vtk.cmake:77 (find_package)
  CMakeLists.txt:92 (include)
  CMakeLists.txt:919 (OCCT_INCLUDE_CMAKE_FILE)


CMake Error at /usr/lib64/cmake/vtk/VTK-targets.cmake:689 (set_target_properties):
  The link interface of target "VTK::RenderingOpenGL2" contains:

    X11::X11

  but the target was not found.  Possible reasons include:

    * There is a typo in the target name.
    * A find_package call is missing for an IMPORTED target.
    * An ALIAS target is missing.

Call Stack (most recent call first):
  /usr/lib64/cmake/vtk/vtk-config.cmake:145 (include)
  adm/cmake/vtk.cmake:77 (find_package)
  CMakeLists.txt:92 (include)
  CMakeLists.txt:919 (OCCT_INCLUDE_CMAKE_FILE)

I don't know if this is because we're not importing enough components at this point, or if there is a vtk issue.

So I think the problem is that OCCT is importing too many components from VTK. If I make this change:

That sounds right to me

BTW - is modules.json and FindNeededModules.py supposed to be installed? It seems like it might be useful to do so.

Seems to be fixed with:

find_package(VTK COMPONENTS CommonCore glew RengeringUI RenderingOpenGL2 QUIET)

Does that seem right?

afair we stopped using glew before 9.4. Which version of VTK are you building ?

FYI @jaswant.panchumarti

This is with 9.3.1 which still has glew support. I haven't been able to get 9.4 to build yet.

ok. In that case its expected to have to look for glew, its a small bug in VTK that have been already fixed (obv, since glew is not even used anymore)

Seems a little odd since for example it does not seem like OCCT references glew in any way.

closed

Circular dep build issue with opencascade

Designs

Child items ...

Activity