> > We are aware of the issues with building VTK separately from ParaView. > Unfortunately, this seems to be an issue inherent in the ParaView > workflow. We've tried to separate them out before, and it hasn't worked > well. We don't have the manpower to maintain such a separation. I think > ParaView is going to be stuck with embedded VTK for a long time to come. >
Could we generate, as an alternative, VTK packages when building ParaView? >From my experience it's feasable... The only trouble, here , is with python plugins..
