Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Pre-requisites to install on Windows? #39
The error is here: https://gist.github.com/81d62825010a6285e4a8 and appears to be line 37:
Pavel's setup is this:
What are the minimum requirements to get this to build? I can make it work with Visual Studio 2010 Pro and the rest of his setup installed, so what is Pavel missing?
@steveworkman: thanks, creating an issue here was in my plan if you couldn't help me on your blog :).
More notes on environment:
I installed Python, Visual C++ 2010 and Windows 7 64-bit SDK by following installation wizard clicking only on 'next' but I believe everything essential should be in the default configuration.
Can't believe it, but I've just sucessfully compiled Contextify! Problem was on my side and I'm sorry I didn't find it earlier. Apparently windows installer of Visual C++ can't install the newest version, after installation you have to install tons of updates via Windows Update and special package of c++ compilers which can be found http://www.microsoft.com/en-us/download/details.aspx?id=4422
referenced this issue
Dec 16, 2012
Hi Guys. I've got the same error
LINK : fatal error LNK1181: cannot open input file 'kernel32.lib' [c:\node_modules\contextify\build\contextify.vcxproj]
During installing the contextify library,
I had W7-64, Ptyhon 2.3 32bit (because of some other dependency somewhere - I think some deps for vim ternjs) and the problem was in that, i was using 64bit version of node, and this was not compatible with python, so changing to 32bit node..
Important is to have either 32bit Node+Python, or 64bit...
I'm receiving the same error that @vire shared. I've completely wiped and reinstalled my Python installation as well as my array of VS2010 packages (And I followed the instructions @TooTallNate shares here). I've tried Node in both 64 and 32-bit flavors.
I'm not sure if this is of import, but the first sign that something's wrong begins after the line:
At which point I receive a stream of yellow warning messages like so:
The "possible loss of data" warnings do catch my eye. Perhaps there's a clue there?
Either way, this comes to an abrupt end with @vire's message above:
Followed by a short debris field as npm tries to make a hard landing:
And that's it. I'm way out of my depth when it comes to actually devising a solution to this. Compilers are a fuzzy, hardly visited area for me, not to mention C++ itself. If anyone has ideas though, I look forward to poking around.
Okay, the strangest thing just happened. I tried going back to a 32-bit install of Node.js to see if it throws a different error message (the message seemed to have changed when I went from 32 to 64-bit, and frankly the "int64 to int" warnings are damned suspicious). This... magically fixed everything. Contextify just installed without a peep, save for a few warnings. I had switched to a 32-bit version earlier, but that was before re-installing the VS2010 packages. Perhaps that's the difference.
It's amazing what happens when you hit things with a stick and shake them around.
*To clarify, the earlier 32-bit install of Node was still not playing nice even after re-installing the VS2010 packages.