wiki:VisIt/build_x86

How to build VisIt with support for in-situ visualization

Building a parallel version of VisIt on your system allows you to configure VisIt that way, that it uses your MPI library and compiler to avoiding incompatibilities.

If you do not need any special configuration use the prebuild packages provided here (link)!

In the following we demonstrate how to build VisIt on the example of VisIt 2.9.2 (from 10/2015).
Please ensure you always use the latest version and replace "X.Y.Z" or "X_Y_Z" by the appropriate numbers.



QUICK HOWTO

Error: Failed to load processor ShellExample
No macro or processor named 'ShellExample' found
Error: Failed to load processor ShellExample
No macro or processor named 'ShellExample' found
Error: Failed to load processor ShellExample
No macro or processor named 'ShellExample' found
Error: Failed to load processor ShellExample
No macro or processor named 'ShellExample' found



DETAILED HOWTO

Info: The following procedure is included in the script compile_visit.sh attached to this site. If it suites your needs use it: (view)

1) download VisIt build script

Error: Failed to load processor ShellExample
No macro or processor named 'ShellExample' found

2) build 3rd party libraries

We build the 3rd party libraries in a separate step first (with "--no-visit").
Check all possible options with "./build_visitX_Y_Z --help".

a) with GCC (module load gcc):

Error: Failed to load processor ShellExample
No macro or processor named 'ShellExample' found

b) with Intel Compiler (module load intel):

Error: Failed to load processor ShellExample
No macro or processor named 'ShellExample' found

This will ...

  • automatic: downloading 3rd-party packages to current directory ...
  • automatic: configure,build packages in subdirectory "<PACKAGE>" ...
    • follow output with "tail -f build_visitX_Y_Z_log"
  • each of the external packages get compiled and installed into a directory prefix of ./visit/<PACKAGE>/<VERSION>/<ARCH>/
    • the corresponding third-library-cmake-settings are created in ./hostname.cmake

3) download VisIt

  • extract visitX.Y.Z.tar.gz to previous build directory
    Error: Failed to load processor ShellExample
    No macro or processor named 'ShellExample' found

4) configure VisIt

  • copy third-library-cmake-settings to visitX.Y.Z
    Error: Failed to load processor ShellExample
    No macro or processor named 'ShellExample' found
  • set default compiler to GCC (module switch …)
  • change director to visitX.Y.Z/src
    Error: Failed to load processor ShellExample
    No macro or processor named 'ShellExample' found
  • run VisIt's-'ccmake .' and generate Makefiles:
    Error: Failed to load processor ShellExample
    No macro or processor named 'ShellExample' found
    • press 'c' to configure
    • check VISIT_PARALLEL=ON, VISIT_FORTRAN=ON
    • press 'c' until 'g' is available
    • press 'g' to generate Makefile

5) compile VisIt

  • build will happen in visitX.Y.Z/src only
    (=> remove and re-extract directory visitX.Y.Z is a complete clean)
    Error: Failed to load processor ShellExample
    No macro or processor named 'ShellExample' found

6) install VisIt

  • create a tar.gz file
    Error: Failed to load processor ShellExample
    No macro or processor named 'ShellExample' found
  • install VisIt from that tar.gz package
    (all symlinks in libraries will be reset to the paths of the machine !!)
    Error: Failed to load processor ShellExample
    No macro or processor named 'ShellExample' found
    • eg. visit2.9.2/src/svn_bin/visit-install 2.9.2 linux-x86_64 /home/vrsw/VisIt/2.9.2/gcc44_ompi18

7) test VisIt

  • add visit path to $PATH
    Error: Failed to load processor ShellExample
    No macro or processor named 'ShellExample' found
  • run VisIt
    Error: Failed to load processor ShellExample
    No macro or processor named 'ShellExample' found



IMPORTANT COMMENTS

  • VisIt should be compiled with GCC (only try Intel Compiler Suite if you really need it, in general it does not work right out of the box (more infos).
    => make sure 'mpicc' 'mpic++' etc. use GCC before you start the build process
  • IceT: may fail if "mpicc --showme:compile" does not return the path to mpi.h as first entry. Check if this is the case.
    If not you might have to set the variables PAR_COMPILER and PAR_INCLUDE before (seems to be fixed in current VisIt version):
    • export PAR_COMPILER=mpicc
    • export PAR_INCLUDE=<'mpicc --showme:compile' with path to mpi.h first>
  • host profiles are located in src/resources/hosts/.
  • this should not be required, as visit should set LD_LIBRARY_PATH on its own ... anyway
    Error: Failed to load processor ShellExample
    No macro or processor named 'ShellExample' found

any feedback welcomed - h.zilken@…, j.goebbert@…

Last modified 8 years ago Last modified on 02/07/16 02:05:40

Attachments (1)

Download all attachments as: .zip

Note: See TracWiki for help on using the wiki.