mipidisaster / mipidisaster/miLibrary
GPIO class uses wiringPi
Open
Nobody has claimed this yet.
help wanted
question
root cause known
- Dominant language
- C++
- Stars
- 0
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
During creation of the GPIO class such that it doesn't use the wiringPi library.
Changes have been captured in a seperate branch
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 by locating the GPIO class and identifying every wiringPi dependency. Review the separate branch mentioned in the issue, if it can be found, and compare its changes with the current implementation. Done means the GPIO class works without wiringPi and its relevant tests or hardware checks pass.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- embedded-iot
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100