Docs: Installation |
![]() |
Example Usages:
Several variables control the configuration and build process of PETSc. They can either be given as arguments to make or be set as environment variables. PETSC_DIR: - this environment/make variable should point to the location of the PETSc installation that is used. You can add export PETSC_DIR=value in your .profile or .sh file or setenv PETSC_DIR value in your .cshrc or .tcshrc file. Multiple PETSc versions can coexist on the same file-system. By changing PETSC_DIR one can switch between the versions PETSC_ARCH: this environment/make variable is used to specify the configuration that should currently be used. It corresponds to the configuration files in bmake/${PETSC_ARCH}. Multiple variants of PETSc libraries can be installed - each variant corresponding to a different PETSC_ARCH. One can switch between using these variants - by changing the value of PETSC_ARCH. If PETSC_ARCH is not set, the configuration from the last time you ran ./config/configure.py will be used. Return to Installation Instructions Cygwin provides UNIX tools on Microsoft Windows. When installing Cygwin make sure you install the following additional packages
Cygwin also has GNU compilers ( gcc, g++, g77) which can be used if Microsoft, Intel, or Borland Group compilers are not availableNote: To insure success of rebaseall - make sure there are no other cygwin processes (except bash) are running like ssh or sshd etc.
Return to Installation Instructions BLAS/LAPACK: these packages provide some basic numeric kernels used by PETSc.
Return to Installation Instructions MPI: This software provides the parallel functionality for PETSc.
Return to Installation Instructions I don't want to use MPI: You can build (sequential) PETSc without an MPI. Run ./config/configure.py --with-mpi=0 ....Return to Installation Instructions Additional Microsoft Windows Notes:Project Files: We provide default project files that work with Microsoft Visual Studio. They are located at ${PETSC_DIR}/projects. Be sure to build the libraries that correspond to the project configuration you are using. Debugger: Running PETSc probrams with -start_in_debugger is not supported on this platform, so debuggers will need to be initiated manually. Make sure your environment is properly configured to use the appropriate debugger for your compiler. The debuggers can be initiated using Microsoft Visual Studio 6: msdev ex1.exe, Microsoft Visual Studio .NET: devenv ex1.exe, Intel Enhanced Debugger: edb ex1.exe, or GNU Debugger gdb ex1.exe. PETSc Win32 front end - win32fe: This tool is used as a wrapper to Microsoft/ Borland/ Intel compilers and associated tools - to enable building PETSc libraries using make and other UNIX tools. For additional info, run ${PETSC_DIR}/bin/win32/win32fe without any options. Return to Installation Instructions Installing with TAU Instrumentation package:TAU
package and the prerequisite PDT
packages need to be installed separately. PETSc provides a wrapper
compiler for TAU. This needs to be invoked with the correct information
for the installed TAU and PDT packages. For eg: ./config/configure.py
--with-mpi-dir=/home/petsc/soft/linux-rh73/mpich-1.2.4 --with-fc=0 --with-cxx=0
-PETSC_ARCH=linux-tau -with-cpp=cpp --with-cc="`pwd`/bin/taucc.py -cc=gcc
-pdt_parse=/homes/petsc/soft/linux-rh73/pdtoolkit-2.2b1/linux/bin/cxxparse
-tau_instr=/homes/petsc/soft/linux-rh73/tau-2.11.18/i386_linux/bin/tau_instrumentor
-tau_include_dir=/homes/petsc/soft/linux-rh73/tau-2.11.18/include
-tau_lib_dir=/homes/petsc/soft/linux-rh73/tau-2.11.18/i386_linux/lib" Return
to Installation Instructions |