Rodrigo Arias
6d584c646c
When running ovniver without LD_LIBRARY_PATH set, the loader couldn't find any ovni installation and therefore was failing to start the program. With this change we set the RUNPATH (not RPATH) of ovniver to the installation libdir, so when no other libovni library is loaded via LD_LIBRARY_PATH the one provided by the same source as ovniver is used. The value of LD_LIBRARY_PATH is also printed so we can determine where it may be loading libovni. Using LD_DEBUG=libs will give more information of the search process. Fixes: https://pm.bsc.es/gitlab/rarias/ovni/-/issues/163 |
||
|---|---|---|
| cfg | ||
| cmake | ||
| doc | ||
| include | ||
| src | ||
| test | ||
| .clang-format | ||
| .gitignore | ||
| .gitlab-ci.yml | ||
| .readthedocs.yaml | ||
| CHANGELOG.md | ||
| CMakeLists.txt | ||
| COPYING | ||
| flake.lock | ||
| flake.nix | ||
| mkdocs.yml | ||
| README.md | ||
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.