Now uses wiringpi2 instead of wiringpi. #9
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I made this change because the install instructions in
README.md
failed (it wouldn't let me build wiringpi-python as I didn't have a necessary C header or something). I thought it'd be nice to get the module working in a more straightforward way, usingpip
to installwiringpi2
(which seems to have supercededwiringpi
) rather than the git submodule method in the readme.This commit means you can just run
sudo pip install wiringpi2
. The only relevant API difference seems to be thatwiringpi.OUTPUT
is nowwiringpi2.GPIO.OUTPUT
inwiringpi2
.I've successfully run a "real world test" with an RF transmitter on my Pi B+, and I also successfully ran the unit test for the RF sender. I'm not able to test the receiver as I don't have a receiver hardware module.
Hope this helps! If the changes I've made don't make sense then that's cool - let me know if I've unintentionally broken anything. This library rocks!