That should work. Ideally we can get packaging XDMF's python module working properly for the next major release. I just created a bug for that task here:
http://paraview.org/Bug/view.php?id=12445 On Mon, Aug 1, 2011 at 11:37 AM, Utkarsh Ayachit < [email protected]> wrote: > I think making the option advanced makes sense. Dave, any objections? > > Utkarsh > > On Sat, Jul 30, 2011 at 1:27 AM, Tim Gallagher <[email protected]> > wrote: > > Hi, > > > > I just built off the master branch (commit 4f0d9672) and I noticed > XDMF_WRAP_PYTHON was no longer an option. > > > > It appears it was set to INTERNAL in commit 7ac1f751, which was due to > the conversation in the mailing list ( > http://markmail.org/message/gapnf4reuazdtfcn), although I'm not sure if it > was made INTERNAL and ON prior to trying to release and just turned to OFF > at last minute because of the problems. > > > > Is fixing the CPack issue high on the priority list so the binaries will > ship with the XDMF python wrapper? If not, can we revert to the > XDMF_WRAP_PYTHON option as advanced and not INTERNAL? > > > > Thanks, > > > > Tim > > _______________________________________________ > > 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
