John, You should talk to Tim Shead. As part of his OverView work, he is implementing a mechanism is ParaView in which you can define a set of plugins which you want loaded upon program startup. The vision is that one day the ParaView application will really be an empty shell the defines its GUI and implementation by opening a set of predefined plugins.
My point is that PARAVIEW_EXTRA_EXTERNAL_PLUGINS may be unnecessary and at some point may be obsolete. -Ken On 1/14/09 6:46 AM, "John Biddiscombe" <[email protected]> wrote: There used to be a PARAVIEW_EXTRA_EXTERNAL_MODULES - which allowed you to compile modules into paraview - in fact it still exists, but probably nobody uses it any more since plugins have improved so much. I have some users who want to compile paraview, and a couple of selected plugins, and then do a single "make install" I've added PARAVIEW_EXTRA_EXTERNAL_PLUGINS to the main paraview cmake, which allows you to enter vtkCSCSCommon;vtkCSCSFluent;vtkCSCSNetCDF etc etc etc and then it prompts for paths to the sources, and compiles them at the same time as paraview itself. Does anyone else need this functionality? Shall I add it to cvs? It's very simple - but does make life easier for the less experienced users (to manage one build instead of two). JB -- John Biddiscombe, email:biddisco @ cscs.ch http://www.cscs.ch/ CSCS, Swiss National Supercomputing Centre | Tel: +41 (91) 610.82.07 Via Cantonale, 6928 Manno, Switzerland | Fax: +41 (91) 610.82.82 _______________________________________________ ParaView mailing list [email protected] http://www.paraview.org/mailman/listinfo/paraview **** Kenneth Moreland *** Sandia National Laboratories *********** *** *** *** email: [email protected] ** *** ** phone: (505) 844-8919 *** web: http://www.cs.unm.edu/~kmorel
_______________________________________________ ParaView mailing list [email protected] http://www.paraview.org/mailman/listinfo/paraview
