Ease the build process for open-source contributors
Open
Nobody has claimed this yet.
CI
enhancement
Impact: Low
test
- Dominant language
- C++
- Stars
- 331
- Forks
- 33
- PR merge metrics
- No merged PRs in 30d
Description
We need to make it easier to build the debugger so the open-source contributors do not need to spend a lot of time setting things up. Here is a list of related tasks:
- #238
- https://github.com/Vector35/binaryninja-api/issues/3407
- Update build instructions in README (https://github.com/Vector35/debugger/commit/38ff454d4be431b0de3af4f19ce6953f710430a8)
- Include instructions for unit testing
- https://github.com/Vector35/binaryninja-api/issues/3385
Contributor guide
No contributing guide indexed for this repository
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 current README build instructions and review commit 38ff454d4be431b0de3af4f19ce6953f710430a8 for the existing setup changes. Check the remaining unit-testing checklist item and issue #3385 to determine the required contributor workflow. Done means the README explains how to run unit tests and the outstanding build-process task is addressed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- build-system, developer-experience, testing
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100