[Paraview] XDMF and release builds

[David Partyka]

I wasn't* aware I should say ;-)

On Fri, Feb 18, 2011 at 9:04 AM, David Partyka <david.partyka at kitware.com>wrote:

> We can probably do this for the final binaries. I was aware that this was
> off by default.
>
>
> On Fri, Feb 18, 2011 at 9:02 AM, Tim Gallagher <tim.gallagher at gatech.edu>wrote:
>
>> Hi,
>>
>> It's probably too late for the binaries already online, and there may be a
>> good reason why it isn't done already, but would it be possible in the
>> future to compile all the release builds with XDMF_WRAP_PYTHON enabled?
>>
>> Our lab needs to do some modification to our data files as we read them in
>> order to keep the memory footprint reasonable -- we do it through a
>> programmable source -- but that requires libvtkXdmfPython. If the release
>> had it built in, we could just use that instead of having to compile from
>> source on 30+ workstations.
>>
>> Just a suggestion -- I'd be interested in hearing if it's a
>> terrible/impossible idea.
>>
>> 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
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.paraview.org/pipermail/paraview/attachments/20110218/f15aada7/attachment-0001.htm>