[vtk-developers] VTK module-specific CMake config files

[Brian Helba]

If VTK is built with *Module_vtkGUISupportQt* enabled, the file *
${VTK_BINARY_DIR}/VTKConfigQt.cmake* is generated at *
GUISupport/Qt/CMakeLists.txt:80*.

In pre-modular VTK, *${VTK_BINARY_DIR}/VTKConfig.cmake* had the following
code:

>   IF(VTK_USE_QVTK)
>     INCLUDE(${VTK_DIR}/VTKConfigQt.cmake)
>   ENDIF(VTK_USE_QVTK)


However, in the current modular VTK, *${VTK_BINARY_DIR}/VTKConfigQt.cmake* is
no longer automatically included from *${VTK_BINARY_DIR}/VTKConfig.cmake* by
any mechanism.

Is there a proper mechanism to recursively include these module-specific
Config files from the main VTKConfig.cmake file (provided the module is
built), or is the package user expected to know about any module-specific
Config files and manually include them?

In this case, since VTKConfigQt.cmake does nothing more than export some
CMake variables to allow later introspection by the package user, failing
to "INCLUDE(${VTK_DIR}/VTKConfigQt.cmake)" does no harm, but I'm curious
about the more general case.

-- 
Brian Helba
Medical Imaging
Kitware, Inc.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/vtk-developers/attachments/20120530/fb94ee2c/attachment.html>