[CMake] Reusing configuration

Fred Fred stan1313 at hotmail.fr
Tue Oct 12 10:15:09 EDT 2010 

Actually the file is included:

find /ParaView-3.8.1/VTK -name vtkMarchingCubesCases.h
/ParaView-3.8.1/VTK/Filtering/vtkMarchingCubesCases.h

this is why I think the problem comes from how cmake build makefiles since the last line should indicate it where to find the header files:

 INCLUDE_DIRECTORIES(/ParaView-3.8.1/VTK)

> Subject: Re: [CMake] Reusing configuration
> From: themiwi at gmail.com
> Date: Tue, 12 Oct 2010 13:45:32 +0200
> CC: cmake at cmake.org
> To: stan1313 at hotmail.fr
> 
> You'll have to ask on the ParaView list as to why this file isn't included in the development package. I'm pretty sure this is a bug.
> 
> Michael
> 
> 
> On 12. Oct, 2010, at 9:42 , Fred Fred wrote:
> 
> > 
> > I still have a problem.
> > Now my CMakeFiles.txt looks like this:
> > 
> > SET(ParaView_DIR /ParaView-Development-3.8.1-Linux-i686/lib/paraview-3.8)
> > FIND_PACKAGE(ParaView REQUIRED)
> > INCLUDE(${PARAVIEW_USE_FILE})
> > 
> > ADD_PARAVIEW_PLUGIN(MyPlugin "1.0"
> >                    SERVER_MANAGER_XML MyPlugin.xml 
> >                    SERVER_MANAGER_SOURCES vtkMyPlugin.cxx)
> > 
> > INCLUDE_DIRECTORIES(/ParaView-3.8.1/VTK)
> > 
> > I just extracted the VTK hierarchy from the source distrib but I suspect that cmake does not find the files because it lacks building information.
> > How to cope with this?
> > 
> > Error trace:
> > 
> > [ 14%] Generating vtkSMXML_MyPlugin.h
> > -- Generate module: MyPlugin
> > [ 28%] Generating vtkMyPluginClientServer.cxx
> > Scanning dependencies of target MyPlugin
> > [ 42%] Building CXX object CMakeFiles/MyPlugin.dir/vtkMyPlugin.o
> > /vtk/vtkLocal/MyPlugin2/vtkMyPlugin.cxx:26:35: error: vtkMarchingCubesCases.h: Aucun fichier ou dossier de ce type
> > 
> > 
> > From: stan1313 at hotmail.fr
> > To: themiwi at gmail.com
> > Date: Mon, 11 Oct 2010 17:29:37 +0200
> > CC: cmake at cmake.org
> > Subject: Re: [CMake] Reusing configuration
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > Of course, I did it actually but I hoped that the cmake configuration could handle it by itself.
> > Anyway, let us go to a more complicated issue: my plugin uses VTK variable and thus requires including vtk header files. I suppose that any "serious" plugin code would do it.
> > The problem is I get a compilation erreur since the file does not exist in the dev binary distrib.
> > So does it mean that it is necessary to instal the PV VTK dir too?
> > 
> >> Subject: Re: [CMake] Reusing configuration
> >> From: themiwi at gmail.com
> >> Date: Mon, 11 Oct 2010 17:18:45 +0200
> >> CC: cmake at cmake.org
> >> To: stan1313 at hotmail.fr
> >> 
> >> Ahh, sorry. I didn't look at the error closely. Try this:
> >> 
> >> $ export LD_LIBRARY_PATH=/ParaView-Development-3.8.1-Linux-i686/lib/paraview-3.8:$LD_LIBRARY_PATH
> >> $ make
> >> 
> >> Michael
> >> 
> >> On 11. Oct, 2010, at 17:09 , Fred Fred wrote:
> >> 
> >>> 
> >>> Actually I did already make the test, ie putting this line on top, but it does not change anything.
> >>> 
> >>>> Subject: Re: [CMake] Reusing configuration
> >>>> From: themiwi at gmail.com
> >>>> Date: Mon, 11 Oct 2010 17:04:22 +0200
> >>>> CC: cmake at cmake.org
> >>>> To: stan1313 at hotmail.fr
> >>>> 
> >>>> Well, the line with the "set(ParaView_DIR ...)" should be before the FIND_PACKAGE call, although one usually sets this variable only in the cache if CMake isn't able ParaView on its own.
> >>>> 
> >>>> Michael
> >>>> 
> >>>> On 11. Oct, 2010, at 16:54 , Fred Fred wrote:
> >>>> 
> >>>>> 
> >>>>> Yes, actually I did not remember that install binaries were now available.
> >>>>> So I did it, managed to build my plugin Makefile but got an error at make time:
> >>>>> 
> >>>>> [ 14%] Generating vtkSMXML_MyPlugin.h
> >>>>> /ParaView-Development-3.8.1-Linux-i686/bin/kwProcessXML: error while loading shared libraries: libvtkCommon.so.pv3.8: cannot open shared object file: No such file or directory
> >>>>> 
> >>>>> I followed the advice on http://www.paraview.org/Wiki/ParaView:Plugin_Deployment_with_Development_Installs
> >>>>> and particularly "set their ParaView_DIR to the development when configuring with CMake"
> >>>>> My CmakeLists.txt is now:
> >>>>> 
> >>>>> FIND_PACKAGE(ParaView REQUIRED)
> >>>>> INCLUDE(${PARAVIEW_USE_FILE})
> >>>>> 
> >>>>> ADD_PARAVIEW_PLUGIN(MyPlugin "1.0"
> >>>>>                  SERVER_MANAGER_XML MyPlugin.xml 
> >>>>>                  SERVER_MANAGER_SOURCES vtkMyPlugin.cxx)
> >>>>> 
> >>>>> SET(ParaView_DIR /ParaView-Development-3.8.1-Linux-i686/lib/paraview-3.8)
> >>>>> 
> >>>>> Any help?
> >>>>> 
> >>>>>> Subject: Re: [CMake] Reusing configuration
> >>>>>> From: themiwi at gmail.com
> >>>>>> Date: Mon, 11 Oct 2010 16:02:51 +0200
> >>>>>> CC: drescherjm at gmail.com; cmake at cmake.org
> >>>>>> To: stan1313 at hotmail.fr
> >>>>>> 
> >>>>>> 
> >>>>>> On 11. Oct, 2010, at 15:47 , Fred Fred wrote:
> >>>>>> 
> >>>>>>> 
> >>>>>>> So it is impossible to just extract the options from the environment config data.
> >>>>>>> But you suggestion is fine although it requires some work lol
> >>>>>>> Thx
> >>>>>>> 
> >>>>>>>> Date: Mon, 11 Oct 2010 09:42:24 -0400
> >>>>>>>> Subject: Re: [CMake] Reusing configuration
> >>>>>>>> From: drescherjm at gmail.com
> >>>>>>>> To: stan1313 at hotmail.fr
> >>>>>>>> CC: cmake at cmake.org
> >>>>>>>> 
> >>>>>>>> On Mon, Oct 11, 2010 at 9:32 AM, Fred Fred <stan1313 at hotmail.fr> wrote:
> >>>>>>>>> Hello,
> >>>>>>>>> I suppose this question has already been asked here but I did not find any
> >>>>>>>>> trace of it, including in the wiki.
> >>>>>>>>> My students want to install PV at home and they need to build it from source
> >>>>>>>>> in order to extend it.
> >>>>>>>>> They do have a version installed at the university and, since configuring
> >>>>>>>>> and choosing the right options is not that easy, I wonder if there is a way
> >>>>>>>>> to give them a configuration file so as for them to have the options
> >>>>>>>>> selection list prefilled?
> >>>>>>>>> 
> >>>>>>>> 
> >>>>>>>> The big problem with that is the install must be in the same folder
> >>>>>>>> and the dependencies must be the same. It may be easier to create a
> >>>>>>>> script to start cmake-gui with a command line containing the options
> >>>>>>>> you will have as default.
> >>>>>>>> 
> >>>>>>>> John
> >>>>>> 
> >>>>>> You can give them a cache-initializer file which they pass to cmake using the -S flag. The file contains "set(... CACHE ...)" statements.
> >>>>>> 
> >>>>>> OTOH, you can also download the "development files" for the binary distributions of ParaView from http://paraview.org/paraview/resources/software.html (under "ParaView Development Installation").
> >>>>>> 
> >>>>>> Michael 
> 
> --
> There is always a well-known solution to every human problem -- neat, plausible, and wrong.
> H. L. Mencken
> 
 		 	   		  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.cmake.org/pipermail/cmake/attachments/20101012/074b9946/attachment-0001.htm>

More information about the CMake mailing list