[vtk-developers] Examples/Build/vtkMy last minute request

[dean.inglis at camris.ca]

Hi Brad,

that's great thanks!  I have updated my
vtkMy equivalents (no cmake script runs to
upgrade classes) and it seems to work fine.

The doxygen stuff works, with the minor 
annoyance that the vtk nightly tag file
doesn't decompress after downloading with wget.
A workaround for this is to build
vtk doxygen doc (takes hours), rename the generated tag file to what the vtkMy doxygen
script expects, and copy that into the 
vtkMy/Utilities/Doxgen build dir.  

I completey forgot that one can have shared and  static builds at the same time ... so the tcl
wrapping should not be a problem.

I'll update the vtkMy readme with some notes
sometime after the release

Dean


> 
> > for those of us who build our own out of source classes
> > using VTK/Examples/Build/vtkMy as a model,
> > I am requesting, hopefully before VTK 4.5 is released,
> > that this example be fully tested under static and shared builds.
> 
> I've updated the CMake code in vtkMy and vtkLocal to modern-style.  I've 
> converted vtkImageFoo to the new pipeline by hand, but I don't want to 
> mess with the conversion script (you'll have to bug Ken Martin for that).
> 
> Getting these tested on the dashboard everywhere is non-trivial, which 
> is why it has not been done and why they get out of date.  A few 
> dashboard machines test them but not on very many configurations.  I've 
> been working on the problem slowly but I can't spend much time on it.
> 
> > It would be great if tcl wrapping worked under static builds
> 
> That would require a vtkmy equivalent of the "vtk" executable and it 
> would have to link and initialize all of VTK's wrappers.  It wouldn't be 
> too hard to implement but I don't want to support it right now.  It is 
> possible to build vtkMy shared even with a static VTK.  Then one can run 
> the main "vtk" executable and load the shared vtkMy* Tcl wrappers.
> 
> > and having doxygen genereated documentation working again 
> > would be a bonus.
> 
> I enabled BUILD_DOCUMENTATION, went into the Utilities/Doxygen 
> directory, and ran "make vtkMyDoxygenDoc".  It seemed to produce 
> documentation as expected.  The implementation only works on UNIX but 
> there is no time to fix it now.
> 
> -Brad
>