[CMake] Reusing configuration

[Michael Wild]

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
>>>> 
>>> 		 	   		  
>> 
>> --
>> There is always a well-known solution to every human problem -- neat, plausible, and wrong.
>> H. L. Mencken
>> 
> 		 	   		  _______________________________________________
> 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 CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ
> 
> Follow this link to subscribe/unsubscribe:
> http://www.cmake.org/mailman/listinfo/cmake

--
There is always a well-known solution to every human problem -- neat, plausible, and wrong.
H. L. Mencken

-------------- next part --------------
A non-text attachment was scrubbed...
Name: PGP.sig
Type: application/pgp-signature
Size: 195 bytes
Desc: This is a digitally signed message part
URL: <http://www.cmake.org/pipermail/cmake/attachments/20101011/b52c0af7/attachment.pgp>