Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

building on v0.11 #16

Closed
seriousManual opened this issue Oct 24, 2013 · 11 comments
Closed

building on v0.11 #16

seriousManual opened this issue Oct 24, 2013 · 11 comments
Assignees

Comments

@seriousManual
Copy link

i made a testbuild on travis on node v0.11.3 which failed.

i did not investigate further, maybe that will be an issue when 0.12 is released.

@seriousManual
Copy link
Author

any plans for 0.12?

@kelly
Copy link
Owner

kelly commented Aug 18, 2014

It will be supported. It appears Buffers have changed which breaks the current version.

@bchr02
Copy link

bchr02 commented Dec 30, 2015

@kelly when do you think this will be complete? We still can't install cylon-i2c on any version of Node greater than 0.10.x .

@bchr02
Copy link

bchr02 commented Dec 30, 2015

Looks like #69 is a duplicate of this issue.

@kelly
Copy link
Owner

kelly commented Jan 1, 2016

@bchr02 the current i2c version works on 0.12.9 and under.

@kelly kelly closed this as completed Jan 1, 2016
@bchr02
Copy link

bchr02 commented Jan 2, 2016

Thanks but when will it work with 0.4.x and 0.5.x?

@kelly
Copy link
Owner

kelly commented Jan 2, 2016

@bchr02 since it requires a full re-write of the c++ code, it's not an immediately a priority for me. If anyone wants to take a shot at it, submit a pull request using NAN and i'll merge it in.

@EMCP
Copy link

EMCP commented Nov 6, 2016

Guessing nothing has changed on this issue since January. I just tried to install this library on a raspbian running pi2, node v6.x.x, and nada

@kelly
Copy link
Owner

kelly commented Nov 6, 2016

@EMCP this is closed, so your issues aren't related to this bug.

@EMCP
Copy link

EMCP commented Nov 6, 2016

I'm just trying to get the status of this project running on versions beyond node .12

@EMCP
Copy link

EMCP commented Nov 6, 2016

strangely, the project that used this library was on an older version 0.1.1 .. after upgrading the errors have dropped away on my platform.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants