-
Notifications
You must be signed in to change notification settings - Fork 15
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
got this when trying to pair #1
Comments
Try this, for macOS |
Will do thanks |
Closing for lack of activity. Reopen if the issue is not resolved. |
brew: command not found |
Did you try installing homebrew? |
Installed homebrew,but when trying to install the plugin I get this: n file included from ../src/dns_service_browse.cpp:1: continuously |
echo Build node-sodium module xcode-select: error: tool 'xcodebuild' requires Xcode, but active developer directory '/Library/Developer/CommandLineTools' is a command line tools instance CXX(target) Release/obj.target/sodium/src/crypto_aead.o Error: make nodesodium exited with code 2 npm ERR! code ELIFECYCLE npm ERR! A complete log of this run can be found in: |
Do you have Xcode installed? Make sure it is and then run |
when i run npm install -g node-appletv
i get this
Static libsodium was not found at /usr/local/lib/node_modules/node-appletv/node_modules/sodium/deps/build/lib/libsodium so compiling libsodium from source.
libtool is required, but wasn't found on this system
make: *** [libsodium] Error 1
/usr/local/lib/node_modules/node-appletv/node_modules/sodium/install.js:287
throw new Error(cmdLine + ' exited with code ' + code);
^
Error: make libsodium exited with code 2
at ChildProcess. (/usr/local/lib/node_modules/node-appletv/node_modules/sodium/install.js:287:19)
at ChildProcess.emit (events.js:160:13)
at Process.ChildProcess._handle.onexit (internal/child_process.js:209:12)
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! [email protected] preinstall:
node install.js --preinstall
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the [email protected] preinstall 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! /Users/Luke/.npm/_logs/2018-03-24T01_10_00_225Z-debug.log
The text was updated successfully, but these errors were encountered: