[vtk-developers] QVTKWidget update

[Wylie, Brian]

Clinton,

What about just having Cmake copy the shared lib to the designer plugins
directory. This way it happens automatically and users don't have to
worry about it. Perhaps we could put a cmake option (defaulted to ON) so
that if people really do want that to happen they can turn it off.

The cmake code would be something like this... (this needs to be cleaned
up a bit is why it's not in vtkSNL yet).

FOREACH( extension ${PLUGIN_EXT} ) 
  ADD_CUSTOM_COMMAND(
    TARGET QVTKWidgetSetPlugin
    POST_BUILD
    COMMAND ${CMAKE_COMMAND}
    ARGS -E copy 
 
${EXECUTABLE_OUTPUT_PATH}/${CMAKE_CFG_INTDIR}/QVTKWidgetSetPlugin.${exte
nsion} 
        ${QT_INCLUDE_DIR}/../plugins/designer
    COMMENT Copying QVTKWidgetSetPlugin.${extension} to Qt plugin
directory
  )
ENDFOREACH( extension )

	Brian Wylie
	Sandia National Laboratories
	MS 0822 - Org 9227 - Building 880/A1-J
      (505) 844-2238   FAX (505) 845-0833
 

> -----Original Message-----
> From: vtk-developers-bounces at vtk.org 
> [mailto:vtk-developers-bounces at vtk.org] On Behalf Of Clinton Stimpson
> Sent: Monday, January 31, 2005 7:13 AM
> To: John Biddiscombe
> Cc: vtk-developers at vtk.org
> Subject: Re: [vtk-developers] QVTKWidget update
> 
> 
> Thanks for the changes to the build.  That's reasonable.
> 
> Also, to answer your other email about the plugin.  I'll CC 
> the vtk-developers because I think others will ask the same thing.
> 
> To put the plugin under the designer, you have to do one of 
> two things.
> Copy the plugin library to $QTDIR/plugins/designer, or if I 
> have ~/plugins/designer for my own plugins, give the 
> ~/plugins path to the qtconfig program.  If you build with 
> QVTK on, and do an install, you'll get a 
> VTK-INSTALL/plugins/designer directory.  You can even give 
> VTK-INSTALL/plugins to the qtconfig program.
> 
> Clint
> 
> Quoting John Biddiscombe <biddisco at cscs.ch>:
> 
> > Clinton
> >
> > > I hope I did the VTK/CMakeLists.txt, 
> VTK/vtkIncludeDirectories, and 
> > > VTK/GUISupport/CMakeLists.txt files correctly.  I tried 
> to find all 
> > > the places to make changes to make GUISupport 
> build/install/etc.. as 
> > > the other VTK kits.
> > >
> > > Have fun.  Examples are found in VTK/Examples/GUI/Qt for 
> those who 
> > > want to try it out.
> >
> > Since I selected
> > "GUI support" ON
> > "Build Qvtk" ON
> > "Build Examples" ON
> >
> > I thought it would be only reasonable to have the Qvtk 
> examples built 
> > as part of the main build. These were not enabled, so I've 
> tweaked the 
> > Cmakelists files in Examples to do an if Qvtk is on, then do Subdir 
> > GUI/Qvtk, and in each of the actual example dirs, there was an 
> > INCLUDE(FindVtk.cmake), which isn't required if the 
> examples are built 
> > as part of vtk itself, so I've surrounded these by an IF (NOT
> > VTK_SOURCE_DIR) which should only be set when building vtk 
> itself, so 
> > you can still build them as part of an external setup if you want. 
> > I've only modified Cmakelists files, so I'm not interfering 
> with the 
> > Qt/Qvtk License :)
> >
> > Linux : All examples working well on my setup. Lovely.
> > Windows. Didn't get anything with the imageviewer demo, but 
> maybe it 
> > choked on my VTK_DATA_ROOT or something. Will have another 
> look back 
> > at home tonight.
> >
> > Many thanks for the classes, I'm sure they'll be very handy 
> for a lot 
> > of people.
> >
> > cheers
> >
> > JB
> >
> >
> 
> 
> _______________________________________________
> vtk-developers mailing list
> vtk-developers at vtk.org
> http://www.vtk.org/mailman/listinfo/vtk-developers
> 
>