- PARAVIEW LINUX HOW TO
- PARAVIEW LINUX PATCH
- PARAVIEW LINUX CODE
- PARAVIEW LINUX FREE
makeParaView -python -mpi -python-lib /usr/lib/x86_ 64-linux-gnu/libpython2. For example in a 64-bit Ubuntu installation, for using the Python 2.7 library: You'll also need to provide the path to the main Python library with the option -python-lib.
If you want to build ParaView with MPI and Python support, you can use the respective options:īut for example in Ubuntu, this doesn't work very well. PARAVIEW LINUX PATCH
If you are able to patch the bug, you don't need to rebuild from the start, because you can use the -no-config option for skipping the step of starting a new build and instead continue with the build:
PARAVIEW LINUX CODE
Imagine that ParaView wasn't successfully built due to some bug in the code that makes it impossible to build with your current Qt version. refers to a CMake build option that is valid for this ParaView version, so that it will copy the Qt libraries into ParaView's own lib/paraview-3.12 folder, so that the custom Qt installation doesn't need to be made available for the whole OpenFOAM installation. 4/bin/qmake PARAVIEW_INSTALL_THIRD_PARTY_LIBRARIES: BOOL=ON makeParaView -qmake $WM_THIRD_PARTY_DIR/platforms/ $WM_ARCH $WM_COMPILER/qt- 4. In order to build with a specific qmake application that is located in a custom path, as exemplified in Installation/Linux/OpenFOAM-2.1.1/CentOS_SL_RHEL - section CentOS 5.8:. makeParaView -qmake $ (which qmake-qt4 ) the path where qmake-qt4 is located is defined in the shell environment PATH): In order to build with a specific qmake-qt4 application (because your system might also have qmake-qt3 or qmake-qt5), which is available in the current search path (i.e. You can redirect all output into a log file, including error messages:. In order to use the default build options and the system's default Qt version:. 0įor making it easier to understand how most of these options work, here are some usage examples: > $WM_THIRD_PARTY_DIR/platforms/linu圆4Gcc/paraview- 3. To add tests and avoid building documentationįor finer control, the build stages can be selected or deselected individually: MakeParaView BUILD_TESTING=ON PARAVIEW_GENERATE_PROXY_DOCUMENTATION=OFF The -no-FEATURE option can be disable these features ( if not already disabled ):ĬMake options start with a capital letter and contain an '='. python-lib PATH path to python library (current value: none ) mesa-lib PATH path to mesa library (current value: /usr/lib64/libOSMesa.so ) Location of mesa headers (current value: /usr/include/GL ) 
major VER specify an alternative major version for special builds version VER specify an alternative version (current value: 3. gcc force g++ instead of the value from $WM_CXX $WM_THIRD_PARTY_DIR/platforms/linu圆4Gcc/qt-VER/bin/qmake qt with extra Qt gui support ( if not already enabled ) qmake PATH with the Qt version corresponding to the qmake path given cmake PATH with the cmake version corresponding to the cmake path given python with python ( if not already enabled ) mesa with mesa ( if not already enabled ) rebuild for repeated builds (-make -install ) *use with caution* It's also supported for OpenFOAM 2.3 and 2.4 as the secondary ParaView version for building with older Linux Distributions that use older Qt versions.įor building this version, OpenFOAM provides inside the ThirdParty-2.* folder the shell script Template:MakeParaView, which has several options for using it, as indicated by the following command: ParaView 3.12 is the default version that is built with OpenFOAM 2.1 and 2.2. Compatible Python versions: 2.6 or 2.7.Compatible CMake versions: 2.8.3 to 2.8.12.Compatible Qt versions: 4.6, 4.7 and 4.8.
PARAVIEW LINUX FREE
Feel free to extend this page with more details.Ģ Requirements for building ParaView 3.12
PARAVIEW LINUX HOW TO
This page aims to mostly explain how to build ParaView 3.12 in Linux, by using OpenFOAM's own makeParaView script.
2 Requirements for building ParaView 3.12.
0 kommentar(er)
