[Paraview-developers] using plugins in pvbatch from static build

[burlen]

That helped, thanks Andy.

I ended up adding the static linked plugin initialization code used in 
pvserver to pvbatch and pvpython. Will be helpful for you and others to 
review.
http://review.source.kitware.com/#/c/12850/1

Burlen

On 09/27/2013 12:15 PM, burlen wrote:
> Oh, I think you hit the nail on the head. pvbatch may not include 
> ./pvStaticPluginsInit.h
> let me try and see if it helps.
>
> On 09/27/2013 11:55 AM, Andy Bauer wrote:
>> Hey Burlen,
>>
>> This is similar to the discussion at 
>> http://markmail.org/search/?q=static+library+plugins+list%3Aorg.paraview.paraview#query:static%20library%20plugins%20list%3Aorg.paraview.paraview%20from%3A%22Andy%20Bauer%22+page:1+mid:itndjtqlvla7dhhc+state:results.
>>
>> Does that help you out at all?
>>
>> Regards,
>> Andy
>>
>>
>> On Fri, Sep 27, 2013 at 2:58 PM, burlen <burlen.loring at gmail.com 
>> <mailto:burlen.loring at gmail.com>> wrote:
>>
>>     Hi All,
>>
>>     How should one use plugins in pvbatch in a static build? In the
>>     batch script the call to LoadDistributedPlugin fails in the
>>     static build however not calling it doesn't work either, non of
>>     the symbols are in the global namespace. On the other hand in in
>>     the GUI's python shell plugins work fine in static builds they
>>     all seem to be automatically loaded.
>>
>>     Burlen
>>     _______________________________________________
>>     Paraview-developers mailing list
>>     Paraview-developers at paraview.org
>>     <mailto:Paraview-developers at paraview.org>
>>     http://public.kitware.com/mailman/listinfo/paraview-developers
>>
>>
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview-developers/attachments/20130927/075d256c/attachment.htm>