Re: [Paraview] Specify value for CMAKE_INSTALL_PREFIX when compiling Catalyst?

Hmm okay. I am going to report this as an issue. Clearly there are some missing links when it comes to building examples with Catalyst editions. https://gitlab.kitware.com/paraview/paraview/issues/16823 On Mon, Aug 15, 2016 at 12:13 PM, Christopher Neal wrote: > When I

Re: [Paraview] Specify value for CMAKE_INSTALL_PREFIX when compiling Catalyst?

When I try that command I see the following after I type ‘make’: /home/neal/software/ParaView/Examples/Catalyst/CxxOverlappingAMRExample/FEAdaptor.cxx:4:23: fatal error: vtkAMRBox.h: No such file or directory #include ^ compilation terminated.

Re: [Paraview] Specify value for CMAKE_INSTALL_PREFIX when compiling Catalyst?

In that case, try the following instead from a clean directory to build the examples using the Catalyst edition. cmake -DParaView_DIR:PATH=/home/neal/software/Catalyst/Catalyst-v5.1.0-Base-Enable-Python-Essentials_build -DBUILD_FORTRAN_EXAMPLES:BOOL=ON

Re: [Paraview] Specify value for CMAKE_INSTALL_PREFIX when compiling Catalyst?

The catalyst edition was built at: /home/neal/software/Catalyst/Catalyst-v5.1.0-Base-Enable-Python-Essentials_build /home/neal/software/ParaView_build is where I built a version of Paraview with Catalyst, development files, and no gui. On 8/15/16, 11:41 AM, "Utkarsh Ayachit"

Re: [Paraview] Specify value for CMAKE_INSTALL_PREFIX when compiling Catalyst?

Chris, Cool. There's indeed a bug in the install rules. I'll have to it fixed. BTW, I am assuming /home/neal/software/ParaView_build is the direcotory where you build the Catalyst edition, is that correct? On Mon, Aug 15, 2016 at 11:38 AM, Christopher Neal wrote: > Hi

Re: [Paraview] Specify value for CMAKE_INSTALL_PREFIX when compiling Catalyst?

Hi Utkarsh, I pointed to my ParaView_build directory and the examples compile without any errors. cmake -DCMAKE_PREFIX_PATH=/home/neal/software/ParaView_build -DBUILD_FORTRAN_EXAMPLES:BOOL=ON /home/neal/software/ParaView/Examples/Catalyst/ Hope this helps, Chris Neal On 8/15/16, 11:19 AM,

Re: [Paraview] Specify value for CMAKE_INSTALL_PREFIX when compiling Catalyst?

I’m not sure I understand 100% what you’re asking me to do. Do you want me to copy the Catalyst examples directory from my ParaView source tree into my Catalyst ‘Essentials’ edition source tree and then run the configure command? Or do you want me to point the ParaView build for the

Re: [Paraview] Specify value for CMAKE_INSTALL_PREFIX when compiling Catalyst?

Chris, I suspect there's a bug in the "install development files" for a Catalyst edition. Can you try pointing the ParaView_DIR for the Catalyst Examples to the Catalyst build directory instead? Does that work? Utkarsh On Mon, Aug 15, 2016 at 11:07 AM, Christopher Neal

Re: [Paraview] Specify value for CMAKE_INSTALL_PREFIX when compiling Catalyst?

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

Re: [Paraview] Specify value for CMAKE_INSTALL_PREFIX when compiling Catalyst?

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 wrote: > Hi All, > > > > I was wondering what the appropriate way

[Paraview] Specify value for CMAKE_INSTALL_PREFIX when compiling Catalyst?

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