Implementation of GPIO control - #30

Can you do an interactive rebase on this to squash down the commits? Also, there's a merge conflict so once you've squashed the commits you'll need to rebase against master.

As I understand this, this rebase is the tool to reorder and cleanup commits.

had to read:
https://robots.thoughtbot.com/git-interactive-rebase-squash-amend-rewriting-history
https://git-scm.com/book/en/v2/Git-Tools-Rewriting-History

done :-)

Since the latest node update the build of wiring-pi fails. Is it possible to update the gcc version from 4.6.3 to 4.9.2 on travis so that travis uses the same version as raspbian?

see also WiringPi/WiringPi-Node#33

@OvisMaximus I got this working here:

https://travis-ci.org/alexbain/lirc_web/builds/102996397

Take a look at the .travis.yml file to see how to force it to use gcc-4.9 and g++-4.9:

https://github.com/alexbain/lirc_web/blob/wiring-pi/.travis.yml

yay!

On Sun, Jan 17, 2016 at 11:14 PM, Alex Bain notifications@github.com
wrote:

@OvisMaximus https://github.com/OvisMaximus I got this working here:

https://travis-ci.org/alexbain/lirc_web/builds/102996397

Take a look at the .travis.yml file to see how to force it to use gcc-4.9
and g++-4.9:

https://github.com/alexbain/lirc_web/blob/wiring-pi/.travis.yml

—
Reply to this email directly or view it on GitHub
#30 (comment).

What do you think about merging this into a devices or a v2 branch instead of master while we finish thinking through how to handle multiple protocols? I'd like to get all of the http device and zwave device into a big shared branch so we can start brainstorming how to refactor.

@pkubat you might be interested in chiming in here, too

devices / v2 sounds really good. I'd love to put my me1 branch into it, there I did some of this refactoring regarding lirc as a device.

The changes to travis.yml did the job - awesome!

Setteling thoughts about V2: the different supported hardware (not only lirc anymore) makes it feel appropriate to switch to a new product (osur). The macro thing comes with breaking changes on the configuration side: V2 is the minimum change regarding semver.

regarding this patch, v1 master isnt the correct branch for this pull request, so I close it.