I followed the Windows installation step for node-gyp and installing Microsoft Visual Studio C++ 2010 Express solved the problem except a few warnings. I did see the library created in the console message. The build process seems looking for [Drive]:\Program Files\Microsoft Visual Studio 10.0\VC\vcpackages\vcbuild.dll which is installed by Visual Studio...
python,ruby,node.js,msbuild,node-gyp
You can tell npm to use Visual studio 2010 by doing this... npm install socket.io --msvs_version=2010 Replace socket.io with the package that is giving the issue. It is also possible to set the global settings for npm: npm config set msvs_version 2010 --global ...
Following the advice of some of my comments and moving just about everything around to more closely match the demo here, I have finally solved my issue and have a working implementation. Thank you to those in the questions that helped.
javascript,node.js,visual-studio-2012,make,node-gyp
unistd.h is a UNIX header file, not found by default on windows. Either replace unistd.h with io.h for almost the same coverage, or use the GNU windows port found here Related: Is there a replacement for unistd.h for Windows (Visual C)? Edit: I just compiled the module with #include <unistd.h>...
Node-gyp is not quite well documented, so statements below are my findings from the project sources. Options for node-gyp are depended on command. These options are listed in configDefs object. Some of them are translated into GYP options, others are not. GYP file name binding.gyp is hard-coded in configure.js GYP...
node.js,amazon-web-services,cross-compiling,node-gyp,aws-lambda
While not really a solution to your problem, a very easy workaround could be to simply compile the native addons on a Linux machine. For your particular situation, I would use Vagrant. Vagrant can create virtual machines and configure them within seconds. Find an OS image that resembles Amazon's Linux...
This is a known issue with gyp/node-gyp that affects all platforms. You might want to add your two cents to that issue.
Nodejs was outdated. Updating nodejs fixxed the Problem
node.js,npm,jsdom,node-gyp,contextify
Seems I found a way by carefully deleting all node-related file and folder on my computer. 0. Context: I previously made several unsuccessful console clean-ups, with sudo apt-get remove --purge nodejs npm topojson followed by ~3 different ways to reinstall nodejs. I tried EACH way, from clean-up to reinstall, between...
In order to install rtpmidi-node on a Windows machine, you should install the Apple Bonjour SDK
Try: setting the environment variable CXX=/path/to/g++ -Ipath/to/include and then restarting the process. If you're using bash this is done by export CXX="/path/to/g++ -Ipath/to/include" /path/to/include being where the missing header Magick++.h is located if that doesn't work you may manually have to set CXX to include the -I in the makefile...
javascript,c++,arrays,node.js,node-gyp
Lets say you have a Buffer, how I normally pass is like this: var buffer = new Buffer([10, 20, 30, 40, 50]); Then to Pass it to the extension: Extension.to_image(buffer, buffer.length And In my native code: NAN_METHOD(to_image) { unsigned char*buf = (unsigned char*) node::Buffer::Data(args[0]->ToObject()); unsigned int size = args[1]->Uint32Value(); As...
Enabling parallel build will not solve you problem, that one is just an informative message. The real problem is you don't have the Visual Studio version that was used to create one of the components Hubot needs. Try this: npm config set msvs_version 2012 (or 2013 if you have that...
Turns out I had a literal LDFLAGS='{} -L/usr/local/opt/openssl/lib' because of something that wasn't being expanded by the shell. Never mind!
Seems like your external library libdds.a uses OpenMP for parallel execution and since it is statically linked you need to provide -lgomp to resolve all the dependencies. I think you can also compile it with -fopenmp instead of -lgomp...
node.js,openshift,sails.js,node-gyp,gyp
My issue appeared when I was trying to add my package manually with the following command npm install sails-postgresql But if I declare the sails-postgresql package in my dependencies (package.json), the package is automatically installed during the deployment without problem.
node.js,socket.io,npm,node-gyp
It looks like you don't have permissions to write to /usr/local/lib/node_modules/node-gyp. You could: give write permissions to user LukeG on /usr/local/lib/node_modules/node-gyp: sudo chown -R LukeG /usr/local rerun the install command using sudo If it's your dev machine we're talking about I would go for the first option, since that's where...
I just found the answer to this in the node-gyp documentation. The solution is to invoke the build process with the --debug flag. That means to invoke node-gyp configure --debug and/or node-gyp build --debug. Then instead of a Release folder a Debug folder will be created. gdb will then automatically...
LASTINPUTINFO structure has member cbSize, that should be initialized: The size of the structure, in bytes. This member must be set to sizeof(LASTINPUTINFO). It's a common way for versioning in Windows API....
node.js,node-webkit,node-modules,node-gyp
Your module's short name will be used in "require" Your 32-bit code (compiled with target=ia32) will work on 64-bit platform, but not the other way around After you have compiled your module for all platforms, it should be enough to pack different zip, .app or .exe versions for different...
node.js,visual-studio-2010,node-gyp
OK so for anyone wondering I just downloaded the header file and added it to the include directory. I could not for the life of me get it to work with any combination of SDKs, service packs, and redistributables.
As previously mentioned, you can install VC++ Express (and the Windows SDK) for free. However, if you are really that bothered by it, you could use a bcrypt API-compatible module that is implemented in pure javascript, however you will see a performance hit. I should also note that there are...
It was a security firewall that was blocking download links.