<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 10pt;
font-family:Tahoma
}
--></style>
</head>
<body class='hmmessage'>
Actually I did already make the test, ie putting this line on top, but it does not change anything.<br><br>> Subject: Re: [CMake] Reusing configuration<br>> From: themiwi@gmail.com<br>> Date: Mon, 11 Oct 2010 17:04:22 +0200<br>> CC: cmake@cmake.org<br>> To: stan1313@hotmail.fr<br>> <br>> 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.<br>> <br>> Michael<br>> <br>> On 11. Oct, 2010, at 16:54 , Fred Fred wrote:<br>> <br>> > <br>> > Yes, actually I did not remember that install binaries were now available.<br>> > So I did it, managed to build my plugin Makefile but got an error at make time:<br>> > <br>> > [ 14%] Generating vtkSMXML_MyPlugin.h<br>> > /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<br>> > <br>> > I followed the advice on http://www.paraview.org/Wiki/ParaView:Plugin_Deployment_with_Development_Installs<br>> > and particularly "set their ParaView_DIR to the development when configuring with CMake"<br>> > My CmakeLists.txt is now:<br>> > <br>> > FIND_PACKAGE(ParaView REQUIRED)<br>> > INCLUDE(${PARAVIEW_USE_FILE})<br>> > <br>> > ADD_PARAVIEW_PLUGIN(MyPlugin "1.0"<br>> > SERVER_MANAGER_XML MyPlugin.xml <br>> > SERVER_MANAGER_SOURCES vtkMyPlugin.cxx)<br>> > <br>> > SET(ParaView_DIR /ParaView-Development-3.8.1-Linux-i686/lib/paraview-3.8)<br>> > <br>> > Any help?<br>> > <br>> >> Subject: Re: [CMake] Reusing configuration<br>> >> From: themiwi@gmail.com<br>> >> Date: Mon, 11 Oct 2010 16:02:51 +0200<br>> >> CC: drescherjm@gmail.com; cmake@cmake.org<br>> >> To: stan1313@hotmail.fr<br>> >> <br>> >> <br>> >> On 11. Oct, 2010, at 15:47 , Fred Fred wrote:<br>> >> <br>> >>> <br>> >>> So it is impossible to just extract the options from the environment config data.<br>> >>> But you suggestion is fine although it requires some work lol<br>> >>> Thx<br>> >>> <br>> >>>> Date: Mon, 11 Oct 2010 09:42:24 -0400<br>> >>>> Subject: Re: [CMake] Reusing configuration<br>> >>>> From: drescherjm@gmail.com<br>> >>>> To: stan1313@hotmail.fr<br>> >>>> CC: cmake@cmake.org<br>> >>>> <br>> >>>> On Mon, Oct 11, 2010 at 9:32 AM, Fred Fred <stan1313@hotmail.fr> wrote:<br>> >>>>> Hello,<br>> >>>>> I suppose this question has already been asked here but I did not find any<br>> >>>>> trace of it, including in the wiki.<br>> >>>>> My students want to install PV at home and they need to build it from source<br>> >>>>> in order to extend it.<br>> >>>>> They do have a version installed at the university and, since configuring<br>> >>>>> and choosing the right options is not that easy, I wonder if there is a way<br>> >>>>> to give them a configuration file so as for them to have the options<br>> >>>>> selection list prefilled?<br>> >>>>> <br>> >>>> <br>> >>>> The big problem with that is the install must be in the same folder<br>> >>>> and the dependencies must be the same. It may be easier to create a<br>> >>>> script to start cmake-gui with a command line containing the options<br>> >>>> you will have as default.<br>> >>>> <br>> >>>> John<br>> >> <br>> >> You can give them a cache-initializer file which they pass to cmake using the -S flag. The file contains "set(... CACHE ...)" statements.<br>> >> <br>> >> 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").<br>> >> <br>> >> Michael <br>> >> <br>> >> --<br>> >> There is always a well-known solution to every human problem -- neat, plausible, and wrong.<br>> >> H. L. Mencken<br>> >> <br>> > <br>> <br>> --<br>> There is always a well-known solution to every human problem -- neat, plausible, and wrong.<br>> H. L. Mencken<br>> <br> </body>
</html>