n.. SPDX-License-Identifier: MIT

Requirements to use LIBRA

Platform Requirements

  • A recent version of Linux.

  • cmake >= 3.21 (cmake on ubuntu)

  • make >= 3.2 (make on ubuntu)

  • cppcheck >= 1.72. (cppcheck on ubuntu)

  • graphviz (graphviz on ubuntu)

  • doxygen (doxygen on ubuntu)

  • gcc/g++ >= 9.0 (gcc-9 on ubuntu). Only required if you want to use the GNU compilers. If you want to use another compiler, this is not required. gcc-9 rather than gcc-8 is required for C++17 because of std::filesystem usage, which does not work well with gcc-8 on ubuntu.

  • icpc/icc >= 18.0. Only required if you want to use the Intel compilers. If you want to use another compiler, this is not required.

  • clang/clang++ >= 10.0. Only required if you want to use the LLVM compilers or any of the static checkers. If you want to use another compiler, this is not required.

  • nvcc >= 11.5. Only required if you want to use the NVIDIA CUDA compilers. If you want to use another compiler, this is not required.

  • lcov if you want to do code coverage.

Compiler Support

  • g++/gcc

  • clang++/clang

  • icpc/icc

  • nvcc

A recent version of any supported compiler can be selected as the CMAKE_<LANG>_COMPILER via command line. The correct compile options will be populated (as in the ones defined in the corresponding .cmake files in this repository). Note that the C and CXX compiler vendors should always match, in order to avoid strange build issues (LIBRA warns if they don’t).

Important

If you are want to use the Intel compiler suite, you will have to download and install it from Intel’s website. It installs to a non-standard location, so prior to being able to use it in the terminal like clang or gcc, you will need to source the compiler definitions (actual command varies by version).

Clang Tooling

All tools must have 14 <= version <= 19.0.

  • Base tooling and clang-check (libclang-19-dev and clang-tools-19).

  • clang-format (clang-format-19).

  • clang-tidy (clang-tidy-19).

Repository/Code Structure

Requirements

  • All C++ source files end in .cpp, and all C++ header files end in .hpp (which they should if you are following the C++ Development Guide).

  • All C source files end in .c and all C header files end in .h (which they should if you are following the C Development Guide).

  • All CUDA source files end in .cu and all CUDA header files end in .cuh (which they should if you are following the CUDA Development Guide).

  • All source files for a repository must live under src/ in the root.

  • All tests for a project must live under the tests/ directory in the root of the project and must end in a configured prefix (see Configure Time) for details. Out of the box, unit tests are expected to end in -utest.{cpp, c}, integration tests are expected to end in -itest.{cpp, c}, and test harness files are expected to end in _test.{c, cpp, h, hpp}.

    This is only required if you want to take advantage of automated test globbing; if you don’t then you can ignore this requirement.

    Obviously, this is ignored unless LIBRA_TESTS=YES.

  • All test harness files for a project must live under the tests/ directory in the root of the project and must end in a configured prefix (see Configure Time) for details. Out of the box, unit they are expected to end in _test.{c, cpp, h, hpp}.

    This is only required if you want to take advantage of automated test globbing; if you don’t then you can ignore this requirement.

    Obviously, this is ignored unless LIBRA_TESTS=YES.

  • If LIBRA_DOCS=ON, project documentation lives under <repo_name>/docs, with a docs/Doxyfile.in defined to generate doxygen documentation.

  • All projects must include a cmake/project-local.cmake in the root of the repository containing any project specific bits (i.e. adding subdirectories, what libraries to create, etc.). See project-local.cmake: How To Hook Into LIBRA for how to structure this file.