How are you building your plugin? I believe that the ADD_PARAVIEW_PLUGIN macro constructs the list of Plugins that get written into the .plugins file.<br><br><div class="gmail_quote">On Thu, May 27, 2010 at 3:54 PM, Mike Jackson <span dir="ltr"><<a href="mailto:mike.jackson@bluequartz.net" target="_blank">mike.jackson@bluequartz.net</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">So then what is the point of having ParaView look in the plugins<br>
directory if it is not going to be used. Why not just have ParaView<br>
look in the "bin" folder (at least on windows)?<br>
<br>
I see there is a file called ".plugins" inside the bin directory. Mine<br>
has the following content:<br>
<br>
<?xml version="1.0"?><br>
<Plugins><br>
<Plugin name="SierraPlotTools" auto_load="0"/><br>
<Plugin name="SurfaceLIC" auto_load="0"/><br>
<Plugin name="AnalyzeReader" auto_load="0"/><br>
<Plugin name="AnalyzeWriter" auto_load="0"/><br>
<Plugin name="NIfTIReader" auto_load="0"/><br>
<Plugin name="NIfTIWriter" auto_load="0"/><br>
</Plugins><br>
<br>
This is missing my plugins although the plugins are "installed" in the<br>
bin directory during the "INSTALL" project build. There is another<br>
file in the build directory called "PluginList.txt" that _does_ list<br>
my plugins though.<br>
<div>_________________________________________________________<br>
Mike Jackson <a href="mailto:mike.jackson@bluequartz.net" target="_blank">mike.jackson@bluequartz.net</a><br>
BlueQuartz Software <a href="http://www.bluequartz.net" target="_blank">www.bluequartz.net</a><br>
Principal Software Engineer Dayton, Ohio<br>
<br>
<br>
<br>
</div><div><div></div><div>On Thu, May 27, 2010 at 3:42 PM, Utkarsh Ayachit<br>
<<a href="mailto:utkarsh.ayachit@kitware.com" target="_blank">utkarsh.ayachit@kitware.com</a>> wrote:<br>
> Mike,<br>
><br>
> That was a conscious decision. We deliberately install all plugin dlls<br>
> in the same directory as the paraview.exe on windows, just to avoid<br>
> missing dlls issues at runtime. Originally, we had the separate<br>
> "plugins" directory to make it easier for users to locate the plugins<br>
> and load them manually. But now, that's a non-issue, since paraview<br>
> explicitly lists all the plugins it's distributed with in the plugin<br>
> manager dialog.<br>
><br>
> Are you saying that the plugins added using<br>
> PARAVIEW_EXTRA_EXTERNAL_MODULES are not being installed at all? If<br>
> that's the case, then it's definitely a bug.<br>
><br>
> As far as the package generation goes, you need to use CPack. Refer to<br>
> this wiki page for details:<br>
> <a href="http://www.paraview.org/Wiki/ParaView:Build_And_Install#Install_ParaView" target="_blank">http://www.paraview.org/Wiki/ParaView:Build_And_Install#Install_ParaView</a><br>
><br>
> Utkarsh<br>
><br>
> On Thu, May 27, 2010 at 12:37 PM, Mike Jackson<br>
> <<a href="mailto:mike.jackson@bluequartz.net" target="_blank">mike.jackson@bluequartz.net</a>> wrote:<br>
>> Pulled ParaView 3.8.0 from Git. Configured with CMake for VS2008 x64<br>
>> with PARAVIEW_EXTRA_EXTERNAL_MODULES listing 4 of my custom plugins.<br>
>> Compiled. Installed. And all the "client" plugins are installed lose<br>
>> into the ParaView-3.8.0/bin directory instead of<br>
>> ParaView-3.8.0/bin/plugins. Also, I have NSIS installed, where is the<br>
>> "PACKAGE" target in the VS Solution or is there another mechanism to<br>
>> use to create the installer?<br>
>> The other (probably more likely) possibility is that I didn't really<br>
>> pull the 3.8.0 tag from git and instead have some other tag.<br>
>><br>
>> # On branch v3.8.0<br>
>> # Changed but not updated:<br>
>> # (use "git add <file>..." to update what will be committed)<br>
>> # (use "git checkout -- <file>..." to discard changes in working directory)<br>
>> #<br>
>> # modified: CMake/FindHDF5.cmake<br>
>> #<br>
>> # Untracked files:<br>
>> # (use "git add <file>..." to include in what will be committed)<br>
>> #<br>
>> # .cproject<br>
>> # .project<br>
>> # Applications/ParaView/Testing/XML/Fractal3D.xml<br>
>> # CMake/AdjustLibVars.cmake<br>
>> # CMake/_FindHDF5.cmake<br>
>> # i386/<br>
>> # x64/<br>
>> no changes added to commit (use "git add" and/or "git commit -a")<br>
>><br>
>> I just tried this with the ParaView 3.8.0 source code .zip file from<br>
>> the <a href="http://paraview.org" target="_blank">paraview.org</a> web site and had the same results. I also built the<br>
>> NSIS installer, and then actually ran the installer and the same issue<br>
>> happens. Bug?<br>
>> _________________________________________________________<br>
>> Mike Jackson <a href="mailto:mike.jackson@bluequartz.net" target="_blank">mike.jackson@bluequartz.net</a><br>
>> BlueQuartz Software <a href="http://www.bluequartz.net" target="_blank">www.bluequartz.net</a><br>
>> Principal Software Engineer Dayton, Ohio<br>
>> _______________________________________________<br>
>> Powered by <a href="http://www.kitware.com" target="_blank">www.kitware.com</a><br>
>><br>
>> Visit other Kitware open-source projects at <a href="http://www.kitware.com/opensource/opensource.html" target="_blank">http://www.kitware.com/opensource/opensource.html</a><br>
>><br>
>> Please keep messages on-topic and check the ParaView Wiki at: <a href="http://paraview.org/Wiki/ParaView" target="_blank">http://paraview.org/Wiki/ParaView</a><br>
>><br>
>> Follow this link to subscribe/unsubscribe:<br>
>> <a href="http://www.paraview.org/mailman/listinfo/paraview" target="_blank">http://www.paraview.org/mailman/listinfo/paraview</a><br>
>><br>
><br>
_______________________________________________<br>
Powered by <a href="http://www.kitware.com" target="_blank">www.kitware.com</a><br>
<br>
Visit other Kitware open-source projects at <a href="http://www.kitware.com/opensource/opensource.html" target="_blank">http://www.kitware.com/opensource/opensource.html</a><br>
<br>
Please keep messages on-topic and check the ParaView Wiki at: <a href="http://paraview.org/Wiki/ParaView" target="_blank">http://paraview.org/Wiki/ParaView</a><br>
<br>
Follow this link to subscribe/unsubscribe:<br>
<a href="http://www.paraview.org/mailman/listinfo/paraview" target="_blank">http://www.paraview.org/mailman/listinfo/paraview</a><br>
</div></div></blockquote></div><br>