Inconsistent target names created by vtk_module_build and vtk_module_wrap_python
Given a module with definition
NAME
MY::Module
LIBRARY_NAME
myModule
vtk_module_build will create a target Module
, while vtk_module_wrap_python will create a target myModulePython
(furthermore, ParaView's paraview_add_plugin would create a target called myModulePlugin
).
Wouldn't it be more consistent, if vtk_module_build created a target called myModule
? Is there any reason for not using the LIBRARY_NAME here?