Hi Richard,<div><br></div><div>To build your plugin inside of ParaView you can Place separate directories for each plugin under ParaView\Plugins. In each directory you would place the source, xml and CMakeLists.txt for each respective plugin. Then in the root of the Plugins directory you will need to modify that CMakeLists.txt file. In that file you will see calls to paraview_build_optional_plugin. Add entries for each of your plugins. The arguments for that macro are.</div>
<div><br></div><div>paraview_build_optional_plugin(<PluginName> <Comment> <Plugin Directory> <Default Enabled/Disabled>)</div><div><br></div><div>Let us know if you need any more help.<br><br><div class="gmail_quote">
On Wed, Dec 15, 2010 at 11:32 AM, Richard Strelitz <span dir="ltr"><<a href="mailto:strelitz@lanl.gov">strelitz@lanl.gov</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
I have 2 related client side plugins-a reader and a filter and an existing<br>
successful build of 3.8 on Windows 7. I would like to add the plugins to<br>
the PV framework; I have had the code and the plugins themselves tested on<br>
a Linux box. What changes do I have to make to the various CMAKE files<br>
and where is the best place to insert the directories that house the code<br>
(.cxx and .h) and the .xml and cmake files. Not that it should matter, I<br>
am using Visual Studio 8 for the build.<br>
<br>
Thanks in advance.<br>
<br>
Richard<br>
<br>
_______________________________________________<br>
Paraview-developers mailing list<br>
<a href="mailto:Paraview-developers@paraview.org">Paraview-developers@paraview.org</a><br>
<a href="http://public.kitware.com/mailman/listinfo/paraview-developers" target="_blank">http://public.kitware.com/mailman/listinfo/paraview-developers</a><br>
</blockquote></div><br></div>