I usually make a separate builds of ParaView and VTK, where both come from the same source tree.
In other words: cd ~/pvsource cvs checkout paraview cd ~/pvbuild ccmake ~/pvsource cd ~/vtkbuild ccmake ~/pvsource/VTK >From the standalone build of VTK you should be able to submit dashboards and they should end up on VTK's cdash page. David E DeMarle Kitware, Inc. R&D Engineer 28 Corporate Drive Clifton Park, NY 12065-8662 Phone: 518-371-3971 x109 On Mon, Oct 19, 2009 at 8:32 PM, David Doria <[email protected]> wrote: > On Sat, Oct 17, 2009 at 10:22 AM, David Doria <[email protected]> wrote: >> I typically use/work on the VTK that is checked out with paraview. >> There seems to be no way to submit an experimental build of VTK from >> inside paraview. Does that seem like a reasonable thing to want to do? >> e.g. >> >> cd .../bin/ParaView3/VTK >> make Experimental >> >> Thanks, >> >> David >> > > Does no one else do this? Should I leave Paraview's VTK alone and use > a separate VTK build? The problem with that is then things can't be > tested using Paraview... > > Thanks, > > David > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Follow this link to subscribe/unsubscribe: > http://www.paraview.org/mailman/listinfo/paraview > _______________________________________________ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView Follow this link to subscribe/unsubscribe: http://www.paraview.org/mailman/listinfo/paraview
