[Paraview] Build failing

Marcus D. Hanwell marcus.hanwell at kitware.com
Sun Nov 7 12:21:13 EST 2010

On Sun, Nov 7, 2010 at 11:58 AM, David Doria <daviddoria at gmail.com> wrote:
> Ah, I thought vtkCommunicator was a ParaView class. I made a fresh
> clone (which got the updated submodule) and then it built fine.
> Is there ever a reason to pull ParaView without also updating the
> submodules? If not, can this be done automatically with a script? It
> doesn't seem to make sense to allow ParaView to be pulled when it
> would go into an invalid state (like it did for me, where the new
> ParaView code depends on the new VTK code). Is there a way to get git
> to work kind of work like a compiler - when a "high level" command is
> issued (i.e. checkout paraview), it checks to see if anything that
> paraview depends on has changed and updates it before updating
> ParaView?

There are many reasons why you might pull ParaView without updating
the submodules. What if you are working on a topic branch in VTK, and
want to check it builds OK with more recent ParaView master? If you do
want to get everything then I added an alias for ParaView,

git pullall

It will update ParaView, and then call git submodule update. I think
this is documented on the wiki page and the one page PDF I added
there. We could possibly make the pullall a little more intelligent
about topic branches in the future, but it should work as advertised
for most.


More information about the ParaView mailing list