[Paraview] Development Install Tree

[Mark Olesen]

On Thu, 2010-03-04 at 16:42 -0500, Dave Partyka wrote:
> Greetings Everyone,
> 
> 
> I have recently commited a fair amount of changes to ParaView that
> lets a developer create a functional development tree that could be
> distributed. The development tree includes all the necessary headers,
> libraries, CMake files and executable tools one would need for
> developing ParaView branded applications and Plugins without building 
> your own ParaView.


For the "hard-test" with PARAVIEW_INSTALL_DEVELOPMENT turned on.

- make && make install
- relocate the built tree somewhere else
- rename the source tree to another name (to check if the source tree
really isn't needed).

After doing this, and setting ParaView_DIR to point to the new location,
building a separate plugin still fails, due to the following bits from
the plug CMakeLists.txt:

   FIND_PACKAGE(ParaView REQUIRED)
   INCLUDE(${PARAVIEW_USE_FILE})


The $ParaView_DIR/ParaViewConfig.cmake is found and it contains
references to the now non-existent paraview source directory.

If I move $ParaView_DIR/ParaViewConfig.cmake out of the way, the
$ParaView_DIR/lib/paraview-3.7/ParaViewConfig.cmake file is correctly
found and the build succeeds.

Is there a make target that I should be using to avoid this (eg, "make
somewhatclean") or should I just move the file out of the way and be
done with it?

/mark



DISCLAIMER:
This electronic transmission (and any attachments thereto) is intended solely for the use of the addressee(s). It may contain confidential or legally privileged information. If you are not the intended recipient of this message, you must delete it immediately and notify the sender. Any unauthorized use or disclosure of this message is strictly prohibited. Faurecia does not guarantee the integrity of this transmission and shall therefore never be liable if the message is altered or falsified nor for any virus, interception or damage to your system.