Go to file
Rodrigo Arias 48df02f102 Always use the project version
Don't duplicated versions so we avoid the problem of missing one
instance to be updated.
2023-07-07 10:42:40 +02:00
cfg Improve colors for Resting and Absorbing states 2023-04-17 17:04:48 +02:00
cmake Add cmake module to check the -fompss-2 flag 2023-05-31 19:15:47 +02:00
doc Document sponge mode and progress events 2023-04-17 17:47:07 +02:00
include Always use the project version 2023-07-07 10:42:40 +02:00
nix Always enable all tests for ovni-rt 2023-05-30 18:16:08 +02:00
src Always use the project version 2023-07-07 10:42:40 +02:00
test Always use the project version 2023-07-07 10:42:40 +02:00
.clang-format Allow single line enums 2023-04-20 10:53:11 +02:00
.gitignore Ignore some directories and tags 2022-09-29 16:51:59 +02:00
.gitlab-ci.yml Don't produce output link for CI 2023-06-26 11:14:53 +02:00
CMakeLists.txt Set project version in CMakeLists.txt 2023-07-07 10:33:23 +02:00
COPYING Add GPLv3 and MIT licenses 2021-11-03 11:32:17 +01:00
mkdocs.yml Move user guide docs to a new directory 2023-03-24 12:08:45 +00:00
README.md Change the readme to markdown format 2022-11-14 10:40:26 +01:00

Ovni logo

The ovni project is composed of a runtime library (libovni.so), which generates a fast binary trace, and post-processing tools such as the emulator ovniemu, which transform the binary trace to the PRV format, suitable to be loaded in Paraver.

The libovni.so library is licensed under MIT, while the rest of tools are GPLv3 unless otherwise stated.

For more information, read the documentation online or take a look at the doc/ directory. You can display the documentation in HTML by running mkdocs serve from the root directory.

To build ovni you would need a C compiler, MPI and cmake version 3.20 or newer. To compile in build/ and install into $prefix use:

$ mkdir build
$ cd build
$ cmake -DCMAKE_INSTALL_PREFIX=$prefix ..
$ make
$ make install

To run the tests you can run (from the build directory):

$ make test

See cmake(1) and cmake-env-variables(7) to see more information about the variables affecting the generation and build process.