Other variables (PATH, LD_LIBRARY_PATH, PYTHONPATH) should never be needed at compile time. For example if both HDF5 and MPI are needed by the current module, we try to detect with which MPI installation HDF5 was compiled, and to offer this one as a default choice for the package itself. The detection of prerequisites is driven by user options.įor example MPI is detected only if option SALOME_USE_MPI is ON.ĭetection of first order prerequisites is based on a _ROOT_DIR variable or on what has been detected in another dependency. The detection logic of CASCADE should make sure Tbb gets included.īeing able to use different versions/installations of the same product, in the system, or generated by the user.įor instance, using the system python 2.7, or a user-compiled python 2.6. GUI CMake files must reference explicitly CASCADE, but never Tbb. Tbb is a prerequisite of second order (level 2) of GUI, Only taking into account the first order prerequisites of a module should be required.ĬASCADE is a prerequisite of first order (level 1) of GUI, Here are the general principles guiding the implementation: This is required since the configuration process itself uses a Python script in which the environment is not overriden: PARAVIS module - on top of some of the KERNEL, GUI and FIELDS prerequisites, the following variables are used:Īt present for a proper build of PARAVIS, the env variables LD_LIBRARY_PATH and PYTHONPATH should be set to contain the HDF5 and ParaView libraries. SCOTCH_ROOT_DIR (optional): Scotch package PARMETIS_ROOT_DIR (optional): ParMetis package QT4_ROOT_DIR: Qt4 package (only some components are loaded)įIELDS module - on top of some of the KERNEL and GUI prerequisites, the following variables are used: If not given, PARAVIEW_ROOT_DIR is used to look for a VTK installation inside the ParaView installation GUI module - on top of some of the KERNEL prerequisites, the following variables are used: This package is not detected explicitly in the KERNEL, but the path is used to complete the PYTHON path given to Sphinx. This package is not detected explicitly in the KERNEL, but the path is used to complete the PYTHON path given to Sphinx.ĭOCUTILS_ROOT_DIR: Docutils package. SPHINX_ROOT_DIR: Sphinx package - requires setuptools and docutils to work properly. MPI_ROOT_DIR: MPI package (see HDF5_ROOT_DIR above) OMNIORBPY_ROOT_DIR: OmniORB Python backend - if not given, OMNIORB_ROOT_DIR will be tried HDF5_ROOT_DIR: HDF5 package - if HDF5 was compiled with MPI support, the corresponding MPI root directory will be exposed automatically (no need to set MPI_ROOT_DIR) PTHREAD_ROOT_DIR: PThread package - typically not need on Unix systems LIBBATCH_ROOT_DIR: LibBatch package - already uses Python, Swig and PThread They can be specified on the CMake command line (with the -D flag) or in the environment. Set(VTK_DIR /home/mehdi/myFolder/programming/lib/VTK-9.0.The following list indicates the expected variables for each module. Set (CMAKE_CXX_FLAGS "-Wsign-compare -Wno-unused-variable -Wno-unused-parameter -Wdeprecated-copy") The CMakeLists.txtfile is as follows: cmake_minimum_required(VERSION 3.20.3) source files are located in src directory and header files in ìnclude directory. I want to compile cpp source code in which VTK, Eigen, PETSc and dealII libraries are included.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |