[Paraview] plugin reader confusion

[Matt Nipper]

I have attached the CMakeLists.txt file. Also, it seems that part of the
problem is that my build of PV didn't originally have open libraries. This
first build was "debug." I compiled a new one overnight with open libraries
as a "release" but this one will not open.

-Matt

On Wed, Apr 1, 2009 at 14:21, Utkarsh Ayachit
<utkarsh.ayachit at kitware.com>wrote:

> Can you post your CMakeList.txt file that you created for your plugin?
>
> 2009/4/1 Matt Nipper <matt.nipper at gmail.com>:
> > I'm trying to add a customized reader into ParaView 3.4.0. I have
> followed
> > the instructions on
> http://www.paraview.org/Wiki/ParaView:Build_And_Install
> > and successfully compiled my own version of PV 3.4.0. I have also created
> > the necessary files according to
> http://www.paraview.org/Wiki/Plugin_HowTo
> > for my new reader, including MyReader.xml, MyReaderGUI.xml, MyReader.cxx,
> > MyReader.h, and CMakeLists.txt. These I have located in a directory
> > C:\ParaView\3.4.0\Plugins\
> > MyPlugin where C:\ParaView\3.4.0\ is my build directory for PV.
> >
> > What I don't understand is how to actually create the plugin from all of
> > this. I'm working on Windows and have Visual Studio 2005 as my compiler.
> I
> > have tried using CMake with the source code location as
> > C:\ParaView\3.4.0\Plugins\MyPlugin but it seems to revert to
> > C:\ParaView\3.4.0\ when it actually runs. It seems that the issue is
> getting
> > my plugin recognized as a "project" inside VS2005 so I can make it into a
> > .dll file, which in turn can be used by PV.
> >
> > I would appreciate any help on this problem.
> >
> > -Matt
> > Student at DTU
> > _______________________________________________
> > 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
> >
> >
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.paraview.org/pipermail/paraview/attachments/20090401/0e101560/attachment.htm>
-------------- next part --------------

# create a plugin that adds a reader to the ParaView GUI
# it is added in the file dialog when doing opens/saves.

FIND_PACKAGE(ParaView REQUIRED)
INCLUDE(${PARAVIEW_USE_FILE})
# The pqReader.xml file contains xml defining readers with their 
# file extensions and descriptions.

ADD_PARAVIEW_PLUGIN(MyPLOT3DReader "1.0" 
	SERVER_MANAGER_XML MyPLOT3DReader.xml
	SERVER_MANAGER_SOURCES vtkMyPLOT3DReader.cxx
	GUI_RESOURCE_FILES MyPLOT3DReaderGUI.xml)

# The Server Manager XML file defines the properties of the reader.
# This example uses the already existing PNG reader but gives it
# another identity in the Server Manager.
# Adding your own reader to ParaView would mean the SourceProxy class
# points to your class.
# ADD_PARAVIEW_PLUGIN(SMMyPNGReader "1.0" SERVER_MANAGER_XML readers.xml)