[Paraview] Client Side plugins dependent on all server side libraries?

Michael Jackson mike.jackson at bluequartz.net
Fri Jun 12 16:52:06 EDT 2009


Is this the new recommended way of doing things? I would really love  
to use the same CMake code to build both as part of the PV compile  
process and outside of it if possible.

Mike

On Jun 12, 2009, at 4:46 PM, David E DeMarle wrote:

> Here is an example of such cmake code (adapted from
> Applications/StreamingParaView)
>
> #define the server side pieces of the plugin
> SET(STREAMING_SS_SOURCES
>  ...
>  vtkVisibilityPrioritizer.cxx
> )
> SET(SERVER_ARGS
>  SERVER_MANAGER_XML StreamingServerWrapping.xml
>  SERVER_MANAGER_SOURCES ${STREAMING_SS_SOURCES}
>  )
>
> #define the gui side piece of the plugin
> IF(PARAVIEW_BUILD_QT_GUI)
>  FIND_PACKAGE(Qt4)
>  IF(QT4_FOUND)
>
>    SET(STREAMING_CS_SOURCES
>      ...
>      pqStreamingDisplayDecorator.cxx
>      )
>
>    # invoke macro to create the streaming view.
>    ADD_PARAVIEW_VIEW_MODULE(
>      IFACES
>      IFACE_SRCS
>      VIEW_TYPE pqStreamingRenderView
>      VIEW_NAME StreamingView
>      VIEW_XML_GROUP views
>      VIEW_XML_NAME Streaming
>      DISPLAY_XML
>      DISLAY_PANEL
>      )
>
>    # arguments to create the client side pieces of the plugin
>    SET(CLIENT_ARGS
>      GUI_INTERFACES
>      ${IFACES}
>      GUI_SOURCES
>      ${STREAMING_CS_SOURCES}
>      ${MOC_SRCS}
>      ${IFACE_SRCS}
>      ${UI_BUILT_SOURCES})
>  ENDIF(QT4_FOUND)
>
> ENDIF(PARAVIEW_BUILD_QT_GUI)
>
> #combine the server and client sides together into a single plugin
> #paraview is smart enough to only load the pieces that make sense
> ADD_PARAVIEW_PLUGIN ( StreamingPlugin "1.0"
>  ${SERVER_ARGS}
>  ${CLIENT_ARGS}
>  )
>
> David E DeMarle
> Kitware, Inc.
> R&D Engineer
> 28 Corporate Drive
> Clifton Park, NY 12065-8662
> Phone: 518-371-3971 x109
>
>
>
> On Fri, Jun 12, 2009 at 4:25 PM, Moreland,  
> Kenneth<kmorel at sandia.gov> wrote:
>> The thing that has seemed odd to me is this compulsion to split a  
>> plugin
>> into server and client pieces.  In my not very humble opinion you  
>> should
>> just place everything in one plugin that is loaded on both client and
>> server, which usually makes things much easier for both plugin  
>> developer and
>> end user.  Add some CMake code to not compile the Qt and GUI stuff  
>> if the
>> ParaView was not built.
>>
>> -Ken
>>
>>
>> On 6/12/09 1:20 PM, "Michael Jackson" <mike.jackson at bluequartz.net>  
>> wrote:
>>
>> Thanks for the info. At least I can stop searching my CMake files..
>>
>> ---
>> Mike Jackson                 www.bluequartz.net
>>
>>
>>
>> On Jun 12, 2009, at 3:16 PM, Utkarsh Ayachit wrote:
>>
>>> That's correct, the client have VTK dependencies as well.
>>>
>>> Utkarsh
>>>
>>> On Fri, Jun 12, 2009 at 2:37 PM, Michael Jackson
>>> <mike.jackson at bluequartz.net
>>>> wrote:
>>> I am trying to write a plugin for ParaView 3.6 which has both a
>>> "client" part that has code ONLY dependent on Qt and a server side
>>> that has code dependent on Qt, Vtk and one of my own libraries which
>>> gets built as part of build system.
>>>
>>>  After having some issues getting this to compile I started tracking
>>> down the dependencies of the Gui side library and the server side
>>> library. Turns out the Gui Side library is dependent on all the
>>> "server side" stuff like all the vtk libraries. Is this correct?
>>> Seems kinda odd to me.
>>>
>>> Thanks
>>> _________________________________________________________
>>> Mike Jackson                  mike.jackson at bluequartz.net
>>> BlueQuartz Software                    www.bluequartz.net
>>> Principal Software Engineer                  Dayton, Ohio
>>>
>>>
>>>
>>> _______________________________________________
>>> 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
>>
>>
>>
>>
>>    ****      Kenneth Moreland
>>     ***      Sandia National Laboratories
>> ***********
>> *** *** ***  email: kmorel at sandia.gov
>> **  ***  **  phone: (505) 844-8919
>>     ***      web:   http://www.cs.unm.edu/~kmorel
>>
>>
>> _______________________________________________
>> 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