makefile.include.arch
files in root/arch
to root/makefile.include
.Take one that most closely reflects your system (hopefully).For instance, on a linux box with the Intel Composer suite:makefile.include
files will have to be adapted to the particulars of your system (see below).makefile.include
, build VASP:makefile.include.arch
files in /arch, and have a look at the description of the commonly used VASP prcompiler flags.makefile.include.arch
files under /arch, or look at the examples below.makefile.include
./src/symbol.inc
root/src/.objects
file that is part of the distribution.makefile.include
by means of:fftw3.f
:fftw3d.F
and fftmpiw.F
include fftw3.f
).fftw3.f
has to be present in /src.makefile.include.arch
files under /arch or look at the examples below.src/makefile
contains a set of recipes to allow for the compilation of objects at different levels of optimization (other than the general level specified by OFLAG). These recipes replace the special rules section of the makefiles in our old build system.FC=mpif90
, FC_LIB may specify a Fortran compiler without MPI supprt, e.g. FC_LIB=ifort
.-Duse_shmem
, one has to add getshmem.o
as well, i.e.,mpicc --show
.-DCUDA_GPU
to build cross-platform sources for GPU, -DUSE_PINNED_MEMORY
to use pinned memory for transfer buffers, and -DRPROMU_CPROJ_OVERLAP
to overlap communication and computation in RPROJ_MU.-DCUFFT_MIN=N
to intercept any FFT calls of size greater than N3 and evaluate on GPU.-DUSE_MAGMA
to use MAGMA for LAPACK-like calls on the GPU.