-
Notifications
You must be signed in to change notification settings - Fork 95
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
Can't install wiring pi #95
Comments
I don't think this software is maintained anymore. Last release was over 2 years ago. |
Do you have |
Does anyone know of an excellent new wiringpi node package, that supports node10+? |
dunno. I've spent all afternoon reading tons of useless docs, only to end up here. Seems wiring pi doesn't care about node since all the repos are 4 years old. Let me know if you find something that works. I'm just going to call my c program from node I guess. |
same error msg here, while installing on my pizero with the newest node-red and node Versions. |
installing according to wiring-pi page description works fine. |
I may have borked my install. I switched to another pi and just ran install and rebuild and it worked fine. One difference is I used the rasping stretch full image in the latter. |
The problem here is that V8 has removed ForceSet method in the V8 version that Node 10 uses. then you can do npm remove wiring-pi |
@viktorbk still won't work at the latest 8.series node.. |
okay seems to have worked with 8.2.0 ../src/wiringPi.cc:773:3: note: in expansion of macro ‘EXPORT_CONSTANT_INT’ |
I solved this problem with my OS Raspbian GNU/Linux 9 (stretch), with Raspberry 3B+ |
Okay, I looked though the v8 docs on how to fix this. Downgrading is not an option for me as the other packages I'm using require node 9 or even node 10 or higher. I'm going to try to create a pull request replacing all instances of |
Well, I solved the //In addon.h, replaced:
target->ForceSet(v8::String::NewFromUtf8(isolate, #name, v8::String::kInternalizedString), arr, static_cast<v8::PropertyAttribute>(v8::ReadOnly | v8::DontDelete));
//With:
target->DefineOwnProperty(target->CreationContext(), v8::String::NewFromUtf8(isolate, #name, v8::String::kInternalizedString), arr, static_cast<v8::PropertyAttribute>(v8::ReadOnly | v8::DontDelete)); However I still get many mystery errors I can't solve. I cut out all the cascading warnings and errors caused by these three. The first I'm completely confused by. #define NODE_MODULE_INIT() \
namespace nodemodule { \
void init(v8::Handle<v8::Object> target); \
} \
void nodemodule::init(v8::Handle<v8::Object> target)
// { Other Stuff }
#define INIT(name) nodemodule::init##name(isolate, target); And NODE_MODULE_INIT() {
#if NODE_VERSION_AT_LEAST(0, 11, 0)
v8::Isolate* isolate = v8::Isolate::GetCurrent();
#endif
INIT(wiringPi);
INIT(softPwm);
INIT(softServo);
INIT(softTone);
INIT(wiringPiI2C);
INIT(wiringPiSPI);
INIT(wiringSerial);
INIT(wiringShift);
INIT(wiringPiISR);
INIT(extensions);
INIT(devlib);
}
NODE_MODULE_DECLARE(wiringPi); Yeah, confusing, I know. This is why I hate excessive use of compiler macros. But regardless, that C code should work fine, so no clue where the error's coming from. Here are the errors:
Shoutout to possibly related issues: |
I tried to install wiring-pi, i used every kind of procedure, but the result is always this. Can someone help me?
npm install wiring-pi
Cloning libWiringPi ... failed.
================================================================================
FATAL: Cloning libWiringPi failed.
Please check install.log and fix any problems. If you're still stuck,
then please open a new issue then post all the output and as many details as you can to
https://github.com/WiringPi/WiringPi-Node/issues
npm WARN [email protected] No repository field.
npm WARN [email protected] No license field.
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! [email protected] install:
/bin/bash ./install.sh
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the [email protected] install script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
npm ERR! /home/pi/.npm/_logs/2018-04-29T15_47_38_327Z-debug.log
The text was updated successfully, but these errors were encountered: