/** \page compile Compiling \section compilepre Prerequisites Make sure that you have the following programs available. Most can be found at any GNU software FTP repository. \section compilepreopt Optional Packages The following packages are not necessary to compile MPQC, but may provide additional features. \section compileconf Configuration You can build MPQC in the source code directory or you can make a companion directory which will be used to hold all of the files generated by the compilation. You may name this directory anything you want. Typically, this directory is named to indicate the architecture (e.g. mpqc.i686-linux) and will be referred to as the target directory below. In the target directory execute the configure command which is located in the SC source directory. Use the absolute pathname to the configure script. This command should build a hierarchy of target directories and the necessary makefiles. Do a configure --help to see a list of options. Options are specified with an equals sign, as in configure --prefix=/usr/local. Some options, such as all the enable and disable options, do not require an argument. Useful options to configure include:
--prefix
Specifies the installation directory. The default is /usr/local/mpqc/version-number
--enable-debug
Options for debugging will be given to the compiler. Use --enable-debug=opt to use both debugging and optimization options.
--with-default-parallel
Gives the default parallism specializations. Can be none for no default or mtmpi for MTMPIMemoryGrp (MPI must be fully thread-safe) and MPIMessageGrp specializations. The parallelism model can be overridden with command line arguments or environmental variables.
--enable-always-use-mpiThis can be given if MPIMessageGrp is to be the only MessageGrp that will be used. This option should be given if the real argc and argv must be given to MPI_Init.
--disable-parallel
Do not try to find communications libraries.
--disable-threads
Do not try to find the multi-thread libraries.
--enable-shared
Use shared libraries. This will reduce the size of executables, if shared libraries are supported on your system.
--disable-static
Do not build libraries for static linking.
--enable-ref-debug
Check for overwrites and overflows of reference counts. Implied by ``--enable-debug''.
--disable-ref-macros
Use template classes for reference counting. The default is to use a CPP macro to generate a class definition.
--enable-cross-compile
If this option is set then the configure script will take care to not execute any compiled test programs.
--enable-shared-libs
This will generate shared objects and link with them instead of standard ``.a'' libraries. This works on a Linux-ELF system.
--enable-components
This will generate CCA components and enable embedded CCA frameworks within MPQC.
--with-build-id
This is used to generate unique shared library names and a unique default prefix for an MPQC installation. Unique shared library names must be used used by package distributors if a non-official ABI is used. The official ABI is GCC-3.2. Earlier versions of GCC are not compatible. Installations with multiple C++ compilers that use shared libraries should use --with-build-id to avoid accidentally dynamically linking with the wrong libraries.
--with-default-memory
This specifies the default memory allocation, which is used in absense of the memory> keyword in user's input. The default is 32 million bytes (roughly, 32 MB).
--with-cc
Gives the name of the C compiler.
--with-cc-optflags
By default configure will attempt to guess a reasonable set of optimization flags. These flags will be overridden by the argument given to this keyword.
--with-cxx
Gives the name of the C++ compiler.
--with-cxx-optflags
By default configure will attempt to guess a reasonable set of optimization flags. These flags will be overridden by the argument given to this keyword.
--with-f77
Gives the name of the FORTRAN compiler.
--without-f77
configure will not try to find a FORTRAN compiler. This can only be used if nothing more than the utility libraries are needed.
--with-ranlib
Gives the name of the archive indexing utility.
--with-ar
Gives the name of the program that makes libraries.
--with-ld
Gives the name of the object linker.
--with-include
Gives directories in which include files should be sought. For example, --with-include="-I/u/local/inc -I/u/cljanss/include"
--with-libs
Specifies libraries that executables should be linked with. For example, --with-libs=-llapack_IRIX.a.
--with-libdirs
Gives the directories in which libraries should be sought. For example, --with-libdirs=-L/usr/local/lib64.
--with-cca-chem-config
Specifies the config script for the cca-chem-generic package (prerequisite for CCA components).
If you would like to further customize your target directory, you can edit src/lib/scconfig.h and lib/LocalMakefile to suit your needs. The next time you run configure, these files and all the makefiles will be overwritten. \subsection compilecca Notes on CCA Configuration \section compilecomp Compilation Now you are ready to build the libraries and executables. Do this by typing make in your target directory. If you are running on a symmetric multi-processor, you can use GNU make to parallelize the compilation. To compile four files at a time, type make -j4. This feature works correctly with GNU make version 3.78.1 or later; for older versions of GNU make use make JOBS=-j4. You can install the executables and data files with make install. You can install the libraries and header files with make install_devel, however, make install must be also be run to install the files needed for run-time support. \section compilecheck Checking the Compilation See \ref mpqcval for instructions for checking your compilation. */