[Paraview] FW: error building my code
Michael Jackson
mike.jackson at bluequartz.net
Mon Jan 12 08:28:21 EST 2009
You should not copy headers from one location to another. What you
need to do is include the proper directory in your compilation
command. My guess is that you are missing an include to one of the Qt
or ParaView directories.
$QTDIR/include/QtCore/QObjectList
So it looks like you are missing the Qt directories. Is this a client
side plugin? Are you using the following in your CMakeLists.txt file
for the plugin:
Find_Package(Qt4)
INCLUDE(${QT_USE_FILE})
_________________________________________________________
Mike Jackson mike.jackson at bluequartz.net
BlueQuartz Software www.bluequartz.net
Principal Software Engineer Dayton, Ohio
On Jan 12, 2009, at 4:32 AM, Natalie Happenhofer wrote:
>
>
> From: nataliehapp at hotmail.com
> To: kmorel at sandia.gov
> Subject: RE: [Paraview] error building my code
> Date: Mon, 12 Jan 2009 10:26:49 +0100
>
> Hi!
> Very well, I used the //BTX and //ETX flags wherever I used the STL
> classes, but now I have another problem:
> Building the code, I get the following error:
>
> Building CXX object Plugins/CMakeFiles/VdcWriter.dir/
> moc_VdcWriterPluginImplementation.obj
> In file included from C:\ParaviewSource\build\Plugins
> \VdcWriterPluginImplementation.h:38,
> from C:\ParaviewSource\build\Pluigins
> \moc_VDCWriterPluginImplementation.cxx:10:
> C:\ParaviewSource\build\Plugins\pqPlugin.h:36:23 QObjectList:No such
> file or directory
> ...
>
> First it asked for the file pqPlugin.h , which I copied to C:/
> ParaviewSource/build/Plugins,
> but the file QObjectList.h I do not find even in the Qt-directory.
> Where do I get that file from or how can I work around that?
>
> thx,
> Natalie
>
>
> From: kmorel at sandia.gov
> To: paul.m.edwards at gmail.com; nataliehapp at hotmail.com
> CC: paraview at paraview.org
> Date: Fri, 9 Jan 2009 08:20:22 -0700
> Subject: Re: [Paraview] error building my code
>
> The error that you are getting is actually from the “client-server”
> wrapper that is generating the code to marshal and unmarshal
> function calls between ParaView client and server. I agree that the
> problem is most likely caused by the use of STL classes. The parser
> does not handle these, so you will have to wrap any portion of your
> header using STL with //BTX & //ETX flags. That is, have a line “//
> BTX” at the start of the portion you want the wrapper to ignore and
> a line “//ETX at the end.
>
> BTW, when including an STL header file, you should prefix the file
> with vtkstd. That is, use “#include <vtkstd/vector>” and “#include
> <vtkstd/string>”. The VTK build creates these special include files
> to help make your STL use more portable. Also, you should prefix
> all of the STL classes and functions with vtkstd:: rather than std::
> (or use the vtkstd namespace in you cxx file). Again, VTK creates
> the vtkstd namespace to be portable to STL implementations that do
> not use the std namespace correctly.
>
> -Ken
>
> On 1/9/09 7:43 AM, "Paul Edwards" <paul.m.edwards at gmail.com> wrote:
>
> One problem is you need the std:: prefix before string and vector.
>
> Regards,
> Paul
>
> 2009/1/9 Natalie Happenhofer <nataliehapp at hotmail.com>
> Hi!
> I encounter yet another problem which is, I believe, independent
> from the library-linking issue.
> Trying to build my code (vtkVdcWriter.h and vtkVdcWriter.cxx) within
> paraview and expecting all the linker errors, I get the following
> error:
>
> [99%] Generating vtkVdcWriterClientServer.cxx
> syntax error
> ***SYNTAX ERROR found in parsing the header file C:/ParaviewSource/
> ParaView3/Plugins/vtkVdcWriter.h before line 49 ***
> ...
>
> I believe it´s an error thrown by the Qt. Does anyone know what´s
> the problem here (the vtkVdcWriter.h file is posted below) or at
> least, how I can get an error message which is at least a bit more
> specific?
>
> vtkVdcWriter.h:
> #ifndef _vtkVdcWriter_h
> #define _vtkVdcWriter_h
>
> #include "vtkProcessObject.h"
> #include "vtkDataSet.h"
> #include <vector>
> #include <string>
>
>
> class VTK_EXPORT vtkVdcWriter : public vtkProcessObject
> {
> public:
> static vtkVdcWriter *New();
> vtkTypeRevisionMacro(vtkVdcWriter,vtkProcessObject);
> void PrintSelf(ostream& os, vtkIndent indent);
>
> //Description:
> // Set or get the file name of the vdc file.
> virtual void SetFileName(const char* fname);
> virtual const char* GetFileName();
>
> //Description:
> // Set the input data set.
> virtual void SetInput(vtkDataSet* ds);
>
> // Description:
> // Get any input of this filter.
> vtkDataObject *GetInput(int idx);
> vtkDataObject *GetInput()
> {return this->GetInput( 0 );}
>
> //Description:
> // Write the XDMF file.
> void Write();
>
> //routines from vapor vdfcreate
> int cvtToOrder(const char *from, void *to);
> int cvtToExtents(const char *from, void *to);
> int cvtTo3DBool(const char *from, void *to);
> int getUserTimes(const char *path, vector <double> &timevec);
>
> int WriteVDF(unsigned int* dims, int numts, int level, string
> coordsystem, string metafilename, string var);
>
>
> protected:
> vtkVdcWriter();
> ~vtkVdcWriter();
>
> vtkSetStringMacro(FileNameString);
> vtkSetStringMacro(MetaFileName);
> vtkSetStringMacro(DataFileName);
> char *FileNameString;
> char *MetaFileName;
> char *DataFileName;
> };
> #endif /* _vtkVdcWriter_h */
>
>
> Could it be a problem using STL-classes here?
>
> thx for any piece of advice,
> Natalie
>
>
> ¡Ingresa ahora a MSN! ¿Quieres saber cómo va a estar el clima
> mañana? <http://tiempo.latam.msn.com/>
>
> _______________________________________________
> ParaView mailing list
> ParaView at paraview.org
> http://www.paraview.org/mailman/listinfo/paraview
>
>
>
>
>
> **** Kenneth Moreland
> *** Sandia National Laboratories
> ***********
> *** *** *** email: kmorel at sandia.gov
> ** *** ** phone: (505) 844-8919
> *** web: http://www.cs.unm.edu/~kmorel
>
>
> ¡Descúbrelo! ¿Qué puedes hacer con el nuevo Windows Live?
> ¡Descúbrelo! ¿Qué puedes hacer con el nuevo Windows Live?
> _______________________________________________
> ParaView mailing list
> ParaView at paraview.org
> http://www.paraview.org/mailman/listinfo/paraview
More information about the ParaView
mailing list