Notes |
|
(0030318)
|
Jean-Christophe Fillion-Robin
|
2013-02-07 09:23
|
|
Hi Goodwin,
Thanks for reporting and identifying the issue.
If possible, would be awesome if you could help us by submitting a patch using Gerrit.
See http://www.vtk.org/Wiki/VTK/Git/Develop [^]
Thanks
Jc |
|
|
(0030879)
|
Dave DeMarle
|
2013-06-03 15:03
|
|
|
|
(0031053)
|
Dave DeMarle
|
2013-06-25 13:17
|
|
Modularization automated many of the lower level facilities, which is probably why this was buried.
Does including vtkExternalModuleMacros (includes vtkModuleMacros (includes vtkMakeInstantiator) work in your case?
|
|
|
(0031146)
|
Orion Poplawski
|
2013-07-19 12:20
|
|
Also, at install time CMake/vtkMakeInstantiator.cmake, CMake/vtkMakeInstantiator.cxx.in, and CMake/vtkMakeInstantiator.h.in are not installed. |
|
|
(0032078)
|
Dave DeMarle
|
2013-12-27 22:21
|
|
|
|
(0033425)
|
Cory Quammen
|
2014-10-02 09:52
|
|
Comment from Marcus Hanwell on the gerrit review for this topic:
"We tried to cut down on what was auto-included, the instantiator is not built by default with VTK anymore, and we are deprecating it. I think people who want to use it should include it explicitly, and they will need additional logic to check that the functionality is even configured."
GDCM is now explicitly including the instantiator stuff itself.
https://github.com/malaterre/GDCM/blob/master/Utilities/VTK/CMakeLists.txt [^]
The recommended course of action should be include(vtkMakeInstantiator) in their own projects. |
|