[Paraview] Compile Errors with ParaView and my own Modules

[Mike Jackson]

OK.. Check that last email.. After Kent Eschenberg let me take a look at a
working project I finally figured out what I was doing wrong.

I had the name of the Server Manager file ending in ".pvsm" which is a no
no. It _must_ end with ".xml" which in hindsight makes complete sense
because it _is_ an xml file. But to have a compile fail solely based on the
file extension and NOT the actual content of the file is a bit restrictive.

Regardless I now have a working project and combined ParaView build.

Thanks to those who contributed time and effort to helping me out.

Mike

On 11/14/06 12:50 PM, "Mike Jackson" <mike.jackson at imts.us> wrote:

> After working with Andy last night it would seem that there is a serious bug
> with the ParaView 2.4.4 Release. If I use the Latest CVS and comment out
> some of the XML then I can get a combined compile of my code and ParaView.
> 
>   I think a new release of ParaView may be coming so I am not holding out
> hope of a fix in the 2.4.4 branch.
> 
> Mike Jackson
> 
> On 11/14/06 5:22 AM, "El Boustany Cristiano" <kriminal at inwind.it> wrote:
> 
>> hi,
>> I've problems writing my own xml files. I read that you already write this
>> file...can you sand me an example of ServerManager and Gui xml files? always
>> if I don't ask you too much.
>> thank you in advance...
>> 
>> bye
>> 
>> ---------- Initial Header -----------
>> 
>> From      : paraview-bounces+kriminal=inwind.it at paraview.org
>> To          : "ParaView at paraview.org" ParaView at paraview.org
>> Cc          :
>> Date      : Sun, 12 Nov 2006 09:56:16 -0500
>> Subject : [Paraview] Compile Errors with ParaView and my own Modules
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>>> I am trying to have my own libraries compiled into ParaView but I am getting
>>> an error that I think is related to the XML files.
>>> 
>>>  I know that everything works as a separate library because I can compile up
>>> everything, launch ParaView, select "Import Package", select my package xml
>>> file and then load my data.
>>> 
>>> I followed the instructions in the ParaView Book to create the
>>> XXXParaViewImport.cmake file. I then went through ccmake and setup
>>> everything in there and then stated compiling.
>>> 
>>> Here is the error:
>>> 
>>> -- Generate module: rendering
>>> -- Generate module: writers
>>> Cannot extract module name from the file:
>>> /Users/mjackson/Projects/Task_4/PVDislocationModules/PVDislocationModules.pv
>>> sm
>>> make[2]: *** [Servers/ServerManager/vtkSMGeneratedModules.h] Error 1
>>> make[1]: *** [Servers/ServerManager/CMakeFiles/vtkPVServerManager.dir/all]
>>> Error 2
>>> make: *** [all] Error 2
>>> 
>>> 
>>> This is on OS X (10.4.8) with the latest Dev Tools (Xcode 2.4.1) although I
>>> am using a Make project and Xcode has nothing to do with this compile.
>>> 
>>> Here is my PVDislocationModulesParaViewImport.cmake file
>>> --------------------------
>>> # specify the name of the module
>>> SET(MODULE_NAME PVDislocationModules)
>>> 
>>> # Specify non wrapped sources
>>> SET (PVDislocationModules_SRCS
>>>     "${PVDislocationModules_SOURCE_DIR}/vtkDislReaderLE.cxx"
>>> )
>>> 
>>> # specify the sources that should be wrapped
>>> SET(PVDislocationModules_WRAPPED_SRCS
>>>     "${PVDislocationModules_SOURCE_DIR}/vtkFCCGlidePlaneFilter.cxx"
>>>     "${PVDislocationModules_SOURCE_DIR}/vtkBurgerVectorFilter.cxx"
>>>     "${PVDislocationModules_SOURCE_DIR}/vtkParadisReader.cxx"
>>> )
>>> 
>>> #-- Set any include Directories this module needs
>>> INCLUDE_DIRECTORIES(${PVDislocationModules_SOURCE_DIR})
>>> 
>>> #-- Invoke this macro to add link libraries to PV
>>> PARAVIEW_LINK_LIBRARIES("${PVDislocationModules_LIBS}")
>>> 
>>> #-- Invoke this Macro to add the sources to paraview and
>>> #-- wrap them for the client server
>>> PARAVIEW_INCLUDE_WRAPPED_SOURCES ("${PVDislocationModules_WRAPPED_SRCS}")
>>> 
>>> #-- Invoke this macro to include non-wrapped sources in the build
>>> PARAVIEW_INCLUDE_SOURCES("${PVDislocationModules_SRCS}")
>>> 
>>> # Place the package configuration file into the build tree.
>>> CONFIGURE_FILE(${PVDislocationModules_SOURCE_DIR}/${MODULE_NAME}.xml.in
>>>                ${PVDislocationModules_SOURCE_DIR}/${MODULE_NAME}.xml @ONLY
>>> IMMEDIATE)
>>> 
>>> # Place the package configuration file into the build tree.
>>> CONFIGURE_FILE(${PVDislocationModules_SOURCE_DIR}/${MODULE_NAME}.pvsm.in
>>>                ${PVDislocationModules_SOURCE_DIR}/${MODULE_NAME}.pvsm @ONLY
>>> IMMEDIATE)
>>> 
>>> PARAVIEW_INCLUDE_SERVERMANAGER_RESOURCES("${PVDislocationModules_SOURCE_DIR}
>>> /${MODULE_NAME}.pvsm")
>>> 
>>> PARAVIEW_INCLUDE_GUI_RESOURCES("${PVDislocationModules_SOURCE_DIR}/${MODULE_
>>> NAME}.XML")
>>> ---------------------------------------------
>>> 
>>> Here is the first part from my GUI XML file
>>> -------------------------
>>> <ModuleInterface>
>>>  <Library name="PVDislocationModules"
>>> directory="/Users/Shared/OpenSource/pvbuild/bin"/>
>>>  <ServerManagerFile name="PVDislocationModules.pvsm"/>
>>> -------------------------------------------------
>>> 
>>> And in the same folder is the PVDislocationModules.pvsm File.  Is there
>>> something wrong with my XML files?
>>> 
>>> I can post my ParaView CMakeCache.txt if needed.
>>> 
>>> Thanks for any help
>>> --
>>> Mike Jackson   Senior Research Engineer
>>> Innovative Management & Technology Services
>>> 
>>> 
>>> 
>>> 
>>> _______________________________________________
>>> ParaView mailing list
>>> ParaView at paraview.org
>>> http://www.paraview.org/mailman/listinfo/paraview
>>> 
>> 
>>