-
Notifications
You must be signed in to change notification settings - Fork 3
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
Unable to compile on Windows 8 #1
Comments
I've gotten this error before, but I'm afraid I can't remember exactly what I did to fix it. Maybe I had to install an older version of Visual C++. Does this article help at all? http://stackoverflow.com/questions/19801072/the-builds-tools-for-v120-platform-toolset-v120-cannot-be-found. Can you post the exact error message? |
Hi, Here is the exact message: (Running node v0.12.7 n VS 2013). Even i opened the sos-device project in VS and the toolset is v120, but still it is failing there also.
D:\Temp\SOS\node_modules\sos-device>if not defined npm_config_node_gyp (node "C:\Program Files\nodejs\node_modules\npm\bin\node-gyp-bin....\node_modules\node-gyp\bin\node-gyp.js" rebuild ) else (node rebuild ) npm ERR! [email protected] install: npm ERR! Please include the following file with any support request: |
I feel like that error message is misleading. It's been a long time since I've opened this project, but VS2013 just sounds too recent. Do you have a build\bindings.sln? Can you open it? When I do the version selector opens it in VS2010, and it builds fine. |
Which version of Node you are running at.. and which version of Studio..i m on 64 bit machine.. |
0.10.29 (x64), and I have both VS2010 and VS2013 |
oh that is the reason. Since u r running in node 10. going ahead from node 12 the way the bindings are done is changed. n since i can't downgrade that is one issue. however it should work on node v12 and ahead as this is the future otherwise we might unable to use this device. |
Oh, that's interesting. What's involved in upgrading to v12? |
The way the bindings are being created has been changed and now the way node V12 provides it is consistent. NAN is the standard. You can read it online and let me know if you are able to build it. |
i think the bindings needs to be changed to NAN. https://github.com/nodejs/nan |
If you can help me to know the controlTransfer syntax to ring the bell on the device that would be great. device.controlTransfer9a,b,c,d,e,function(err,data)){} . |
I put together some documentation for the hid report protocol. Just converted it to markdown, so the formatting may be a little off. Let me know if you have any questions: https://github.com/AutomatedArchitecture/SirenOfShame/wiki/Hardware-API |
Thanks that looks great. I have some sample code for getting the descriptor from the Device via node V12. Can you help me to transform this code ( by placing exact bytes) to play the sound . var list = usb.getDeviceList(); |
There's a "Sample Send Packet" at the end of that page. Basically: 01FFFFFFFFFFFFFFFF00FFFFFFFFFF0000000000000000000000000000000000000000000000 |
ya, i saw it tha'ts great, however, if you can help out it to translate in the call as i have shown above. the FFFFFF at the start and the length/data is confusing me. I had just started creating it today, so sorry for asking basic questions. |
No worries. It might be easier to transfer it the way the original code does at https://github.com/AutomatedArchitecture/node-sos-device/blob/master/src/nodeSos.cpp#L305 using a UsbControlPacket, but I guess if the code you have above is close (and honestly it looks a bit odd to me) then perhaps this is what you're looking for: device.controlTransfer(0x01, 0xFF, 0xFF, 0xFF, 0xFF, 0xFF, 0xFF, 0xFF, 0xFF, 0x00, 0xFF, 0xFF, 0xFF, 0xFF, 0xFF, 00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, function(err, data)... |
Thanks a ton. i will try tommorrow and let you know the results and then we can work on the bindings for node v12. |
Hi, Iprichar |
This is what we tried, but it is returing with Error: "LIBUSB_ERROR_NOT_FOUND" errno: -5 , Here is the code. var vendorId = 5840; var buf = new Buffer([0x01, 0xFF, 0xFF, 0xFF, 0xFF, 0xFF, 0xFF, 0xFF, 0xFF, 0x00, 0xFF, 0xFF, 0xFF, 0xFF, 0xFF, 00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, //Control transfer 1 - prepare device //Control transfer 2 - prepare device //Control transfer 3 - Request value process.stdout.write("Searching for device 0x"+vendorId.toString(16)+" 9x"+productId.toString(16)+"..."); device.open(); device.controlTransfer(0x21,0x09,0x0200,0x01,buf1, function(err,data)
}); //Get interface //Gotta claim away from OS (should hear windows disconnect device sound) var configurationDescriptor = device.configurationDescriptor; var endpoint = interface.endpoints[0]; console.log("DEVICE ENDPOINTS = ", interface.endpoints.length) ; |
Hi Team,
I am unable to compile this. afer doing on npm install on nodejs v0.12.7, it gives an error related to windows tools v120 is not present. However I have VS2013 perfectly set up. Even i tried to download and install MS build tools but it is of no help.
Can anyone tried this on windows 8.
The text was updated successfully, but these errors were encountered: