Search path handling?
Open
Nobody has claimed this yet.
enhancement
help wanted
partially done
- Dominant language
- CMake
- Stars
- 9
- Forks
- 16
- PR merge metrics
- No merged PRs in 30d
Description
Right now the main consumer of this (OSVR-Core) handles search-path issues itself, but it could reasonably be seen as this library's problem. I started a little bit on this, using some OSVR-Core code, here: https://github.com/OSVR/libfunctionality/tree/binary-location but it's not connected to any of the API functions.
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 by reviewing the binary-location branch and the OSVR-Core search-path handling referenced in the issue. Then identify which API functions should expose this behavior; done means the search-path handling is connected to those API functions and the expected behavior is documented or tested.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cmake
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100