[Paraview] Reader plugins in static builds ignored?

Utkarsh Ayachit utkarsh.ayachit at kitware.com
Fri Nov 23 16:32:40 EST 2012


Sven,

I've pushed a fix for this:http://paraview.org/Bug/view.php?id=13674.
Thanks for catching this issue. If you could test this out, that'd be
great.

Utkarsh

On Fri, Nov 23, 2012 at 3:27 PM, Utkarsh Ayachit
<utkarsh.ayachit at kitware.com> wrote:
> Good catch! I am looking into it.
>
> Utkarsh
>
> On Fri, Nov 23, 2012 at 12:17 PM, Sven Buijssen
> <sven.buijssen at tu-dortmund.de> wrote:
>> Hi,
>>
>> I'm seeing that with static builds of ParaView 3.14.1 and git/master reader
>> plugins can be successfully built along with ParaView, but not actually accessed
>> from the GUI:
>>
>> AdiosReader, AnalyzeNIfTIReader, H5PartReader as well as custom readers do get
>> statically linked into e.g. the paraview binary, but the ParaView GUI (built-in
>> mode) lists no entries that correspond to the
>> ServerManagerConfiguration/Hints/ReaderFactory XML in neither the FileOpen
>> dialog nor the OpenDataWith dialog.
>>
>> I'm wondering whether this is something confined to my setup, whether the
>> mentioned reader plugins are missing some initialization code for static builds
>> or whether this is just an issue not yet documented in the bug tracker.
>>
>> Thanks,
>> Sven
>> _______________________________________________
>> 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


More information about the ParaView mailing list