Incompatibility with nan 2.2.0 #12
Assignees
Comments
|
@hgwood , Thanks for reporting this. We need to upgrade our shim to support latest nan.h. We will get it fixed sooner. |
|
Ah, so it's not just my environment issue... |
|
We'll fix this in next release, meanwhile a temporary workaround is |
|
@jianchun Tried in a different order (install |
|
@jianchun Why not commit a fixed |
|
@hgwood Good suggestion. Will do. Thanks! |
|
I still get compile errors using the new version, though they are different.
|
|
@hgwood the latest installer supports 2 app models for node.js and it installs the necessary binaries for the same.
UWP apps are a Windows 10 feature. For this app model you no longer need to do Console apps, which is the traditional command line based Node.js workflow, is powered by |
|
@aruneshchandra Well that's the point. Many of us want to actually install |
|
Here's the installer for Chakra-based node, which you can use to run console scripts and also use UWP. Please be advised that this will only work with the latest Windows 10 builds. |
It should get installed under |
|
@arjunbijanki Thanks for the info. Like @RReverser, I'm looking to write Node.js console scripts that can call UWP APIs (the Bluetooth 4 stack in particular). I'm aware of the Windows 10 November requirement. The installer you provided in your second answer makes
Doing this ends up with the compile errors I mention in my third message. |
|
@hgwood , once we have concrete plans on next version of bundle installer (whether to replace Thanks for bringing this to our attention! |
|
Sounds good. Since the issues with nan have been resolved, I'll close this issue. Thanks again! |
hgwood
added a commit
to hgwood/winble
that referenced
this issue
Jan 28, 2016
|
@hgwood How did you manage to build this? I'm still failing, but with different errors so not sure whether it's same issue or another one. |
|
@RReverser I can't see any clue in your output... Could you please try "npm i uwp --verbose"? Relevant link lib info would be |
|
@jianchun Well, |
|
Also tried with Node (chakracore) instead, but apparently it's not yet supported, as getting same errors we discussed previously here: |
|
Your link command line was missing some libs. You have only 2 libs listed: This is mine: Those libs are supposed to be brought in by |
|
@jianchun Well... what am I missing then? (where do I get them from?) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
npm install uwpgave me some compile errors (please forgive my localized msbuild printing some messages in French):Since the errors were clearly complaining about nan, I thought I would check the version of nan that was used. Your
package.jsonmentions^2.1.0, which resolved to2.2.0. I guessed that maybe you didn't testuwpwith nan2.2.0, so I cloned this repo on my disk, changed the nan version inpackage.jsonto~2.1.0, rannpm i /path/to/my/cloned/uwpand it worked.So maybe nan messed up and there is a breaking change between 2.1 and 2.2, or maybe uwp is using some internal nan APIs that were changed between 2.1 and 2.2. Anyway, a quick fix is to change the
package.jsonnan dependency to~2.1.0or even2.1.0.The text was updated successfully, but these errors were encountered: