Corto libraries and applications hardcode the path to dependencies for security reasons and to be able to refer to hierarchically organized libraries.
This is however inconvenient when corto libraries need to be embedded in other projects, as libraries are required to be installed to a fixed location, whereas many projects use mechanisms like LD_LIBRARY_PATH to discover libraries.
To make it easier to handle such usecases, the buildsystem shall build two libraries for each project, one is installed to the hierarchical package repository, and another redistributable version is generated that does not link with hardcoded paths, and is installed together with all other redistributable versions.
Corto libraries and applications hardcode the path to dependencies for security reasons and to be able to refer to hierarchically organized libraries.
This is however inconvenient when corto libraries need to be embedded in other projects, as libraries are required to be installed to a fixed location, whereas many projects use mechanisms like
LD_LIBRARY_PATHto discover libraries.To make it easier to handle such usecases, the buildsystem shall build two libraries for each project, one is installed to the hierarchical package repository, and another redistributable version is generated that does not link with hardcoded paths, and is installed together with all other redistributable versions.