Hi Utkarsh,
I have one more question related to the Catalyst edition. I have compiled the
‘Essentials’ build. I used the command below(for reference) to configure the
edition, and everything seems to work out.
./../Catalyst-v5.1.0-Base-Enable-Python-Essentials/cmake.sh
-CMAKE_INSTALL_PREFIX:PATH=/home/neal/software/Catalyst/Catalyst-v5.1.0-Base-Enable-Python-Essentials_build
-DPARAVIEW_INSTALL_DEVELOPMENT_FILES:BOOL=ON
../Catalyst-v5.1.0-Base-Enable-Python-Essentials
I’m trying to compile the Catalyst examples that are located in the original
ParaView source tree using the Catalyst edition. I used the following command
to configure the examples:
cmake
-DCMAKE_PREFIX_PATH=/home/neal/software/Catalyst/Catalyst-v5.1.0-Base-Enable-Python-Essentials_build
-DBUILD_FORTRAN_EXAMPLES:BOOL=ON
/home/neal/software/ParaView/Examples/Catalyst/
cmake does not complain when I configure with the command above. But when I
type ‘make’ I see an error that a header file cannot be located. It’s a header
file that I know for a fact is located in the ‘Essentials’ build directory
under …/include/paraview-5.1.
I tried using the -DCMAKE_INCLUDE_PATH=[path to …/include/paraview-5.1] , but
cmake tells me that the manually specified variable was not used. The full
line that I’m trying to use to configure the examples is:
cmake
-DCMAKE_PREFIX_PATH=/home/neal/software/Catalyst/Catalyst-v5.1.0-Base-Enable-Python-Essentials_build
-DBUILD_FORTRAN_EXAMPLES:BOOL=ON
-DCMAKE_INCLUDE_PATH=/home/neal/software/Catalyst/Catalyst-v5.1.0-Base-Enable-Python-Essentials_build/include/paraview-5.1
/home/neal/software/ParaView/Examples/Catalyst/
Am I not specifying the include path correctly?
Thank you,
Chris Neal
On 8/15/16, 10:15 AM, "Utkarsh Ayachit" <utkarsh.ayac...@kitware.com> wrote:
Chris,
Some thing like this should do the trick:
> [...]/cmake.sh -DCMAKE_INSTALL_PREFIX:PATH=/tmp/install [... path to
Catalyst src ...]
Utkarsh
On Fri, Aug 12, 2016 at 5:49 PM, Christopher Neal
<chrisn...@snumerics.com> wrote:
> Hi All,
>
>
>
> I was wondering what the appropriate way to specify a value for the cmake
> variable CMAKE_INSTALL_PREFIX is when compiling a Catalyst edition. The
> editions make use of a cmake.sh script, and I’ve just been manually adding
> the variable to that file because I can’t quite figure out how to tell the
> script to also use a value for CMAKE_INSTALL_PREFIX that I pass to it.
>
> Does anyone have experience with doing this? I ask because I always want
to
> change the install directory to be a different location than the default
> location in the root directory that Catalyst usually tries to install in.
>
>
> Thank you,
>
> Chris Neal
>
>
> _______________________________________________
> 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 ParaView Wiki at:
> http://paraview.org/Wiki/ParaView
>
> Search the list archives at: http://markmail.org/search/?q=ParaView
>
> Follow this link to subscribe/unsubscribe:
> http://public.kitware.com/mailman/listinfo/paraview
>
_______________________________________________
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 ParaView Wiki at:
http://paraview.org/Wiki/ParaView
Search the list archives at: http://markmail.org/search/?q=ParaView
Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/paraview
