how to avoid shared-library conflict trouble
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 160
- Forks
- 113
- Avg merge
- 12d 15h
- Merged PRs (30d)
- 1
Description
We will have more and more trouble with shared libraries. Most importantly this will hit is more with the HDF5 library. On linux, we have system HDF5 libraries, some distributed with Python, some with MATLAB. Ideally we just use the one that STIR was compiled with.
Some links
https://gitlab.kitware.com/cmake/community/-/wikis/doc/cmake/RPATH-handling
https://cmake.org/cmake/help/latest/manual/cmake-packages.7.html#creating-relocatable-packages
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the linked CMake RPATH-handling and relocatable-packages guidance, then trace how STIR is compiled against HDF5 on Linux. Done means STIR consistently uses the HDF5 library it was compiled with rather than conflicting system, Python, or MATLAB libraries.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cmake, cpp, linux
- Domain
- build-system, infrastructure
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100