-
Notifications
You must be signed in to change notification settings - Fork 26
build: missing libs in LINK command line #20
Comments
@munyirik Do you see any clue? Any possibility |
Right. --node_win_onecore=false should be used. I should fix it so that it's the default behavior. |
I assume the default is indeed false? Don't know how to make it false on command line. |
Actually yes. I just tried to repro but I don't see that error (with just "npm i uwp"). Which version did you use? (I used this). I also see another issue where PATH isn't update to use the most recent Node.js (Chakra) install. Or maybe this should be by design. |
If I run |
I'm using the same (and you can see in my logs in mentioned comment that Node.js reports the same version, so it's not PATH neither). So what is the workaround? Should I do smth like |
Modify C:\Program Files\NodejsUwp\Console\node_modules\npm\node_modules\node-gyp\addon.gypi to set node_win_onecore=false. So at the beginning of the file you'll have this: |
Umm... okay, thanks, I'll try that in the evening on my home laptop. Although it looks like, if it works, it's just a temporary solution that still needs to be backported to Node.js (chakra)? |
With that default to 'false', "npm i uwp" should work. Yes, we'll need to fix Node.js (chakra). Haven't figured out how it worked on our boxes yet. |
Ok, I figured out how it was supposed to work. The log had:
That
The variables section contains
@RReverser Could you please help us do a little debugging? Try git clone this repo to a local dir. Then with Node.js (chakra), run "npm install" in that dir. If it fails, see what you have in |
Okay, first of all - trick with |
@jianchun So with This is the contents of
So it looks like by default Although
Hopefully this helps. |
@RReverser Thanks for spending time on this. This is very weird. I wish I could debug on a repro machine. In our code "node_win_onecore" and "node_uwp_dll" usages are exactly the same. No reason for following to appear in
They should both either take defaults from
@RReverser Could you check if you have this env variable? If not, with a clean Node.js (Chakra) install (undo addon.gypi customization), launch Node.js (Chakra) command prompt, |
|
I stepped that code in debugger. NPM command line parser already converts I suspect that patch will make |
Oh ok, then my assumption was wrong, sorry. So... I removed all the Node.js versions I had to be sure I have clean env. reinstalled Node.js (chakra) 5.6.0 x64, and still getting same results 😞 |
Interesting that when I do smth like |
True, npm does some magic conversions.
I am lost on why you have "node_win_onecore": "". Anyway, next Node.js (chakra) release will have a fix for this. We'll no longer compare with 'false'. Only compare with 'true'. That's should make it work on your box... |
Okay, nevermind, I found the source where that variable was taken from. Although I'm still surprised as I don't remember adding it manually, but maybe I just added it for whatever reason and forgot... weird anyway. The npm code you mentioned contained call to It's still unclear to me how this option got there, or why Sorry for the taken time. |
Oh! Great! Thanks, didn't realize there is another store for npm config. That config option is weird. @munyirik |
Great! So just to be clear, @RReverser you added that line manually? just want to be sure it wasn't automatic :-) |
@munyirik That's what I'm wondering, too. If I added it manually, then it was a rather long time ago and for a good reason, but I can't recall it 😄 |
Ok, thanks and let us know if you run into any other issues. @jianchun I'll still make the change you mention so we don't compare to false. |
@RReverser Thanks a lot for helping us resolving this mystery! @munyirik Sure. |
@jianchun Thank you for your time! |
Reported by @RReverser in #12. We should have a list of libs on LINK command line.
Those libs are supposed to be brought in by
C:\Program Files\NodejsUwp\Console\node_modules\npm\node_modules\node-gyp\addon.gypi
:But @RReverser only has 2:
The text was updated successfully, but these errors were encountered: