• MPI
• HPX
• blaspp
• lapackpp
• Intel MKL or other LAPACK implementation
• cuBLAS (optional)
• GoogleTest (optional; bundled) - unit testing
• Doxygen (optional) - documentation

Using DLAF in a CMake project is extremely easy!

Let's use the variable $DLAF_ROOT for referring to the install path of DLAF.

Configure your project with:

cmake -DDLAF_DIR="$DLAF_ROOT/lib/cmake" ..

Then, it is just as simple as:

find_package(DLAF)

# ...

target_link_libraries(<your_target> PRIVATE DLAF)

The documentation can be built together with the project by enabling its generation with the flag BUILD_DOC=on and then use the doc target to eventually generate it.

# from the build folder, if you have already configured the CMake project
cmake -DBUILD_DOC=on .
make doc

Alternatively, the documentation can be generated independently by using doc/Doxyfile.in, which is a template configuration file in which you have to replace the text ${DLAF_SOURCE_DIR} with the root folder of DLAF containing the source code (e.g. where you cloned this repository).

As a shortcut for this process a doc/Makefile is available, which automatically performs the substitution and then generates the documentation.

cd doc
make doc

The development of DLAF library would not be possible without support of the following organizations (in alphabetic order):

	CINECA: Cineca Consorzio Interuniversitario
	CSCS: Swiss National Supercomputing Centre
	ETH Zurich: Swiss Federal Institute of Technology Zurich
	PASC: Platform for Advanced Scientific Computing
	PRACE: Partnership for Advanced Computing in Europe As part of IP6 WP8