wrong path to node-gyp bin #1760

ShaMan123 · 2019-05-23T07:42:40Z

Node Version: 10.15.3 -> 8.16.0
Platform: Windows
Compiler:
Module: trying to deploy firebase functions and thinking it is related. Using Canvas but it works and builds.

Verbose output (from npm or node-gyp):

C:\WINDOWS\system32>node-gyp --python C:\Python27\python.exe

C:\WINDOWS\system32>if not defined npm_config_node_gyp (node "C:\Users\DELL\AppData\Roaming\npm\node_modules\npm\node_modules\npm-lifecycle\node-gyp-bin\\..\..\node_modules\node-gyp\bin\node-gyp.js" --python C:\Python27\python.exe )  else (node "" --python C:\Python27\python.exe )
module.js:550
    throw err;
    ^

Error: Cannot find module 'C:\Users\DELL\AppData\Roaming\npm\node_modules\npm\node_modules\node_modules\node-gyp\bin\node-gyp.js'
    at Function.Module._resolveFilename (module.js:548:15)
    at Function.Module._load (module.js:475:25)
    at Function.Module.runMain (module.js:694:10)
    at startup (bootstrap_node.js:204:16)
    at bootstrap_node.js:625:3

C:\WINDOWS\system32>node C:\Users\DELL\AppData\Roaming\npm\node_modules\npm\node_modules\node-gyp\bin\node-gyp.js list
gyp info it worked if it ends with ok
gyp info using node-gyp@3.8.0
gyp info using node@8.16.0 | win32 | x64
10.13.0
10.15.3
10.2.1
8.16.0
9.10.0
gyp info ok

The module exists in this path C:\Users\DELL\AppData\Roaming\npm\node_modules\npm\node_modules\node-gyp\bin\node-gyp.js. There's an error resloving the path.

I downgraded node10 to node8. This bug seems to live in npm@node10 because after reinstalling npm on node8 this bug disappeared.

The text was updated successfully, but these errors were encountered:

ShaMan123 · 2019-05-23T09:35:10Z

npm uses node-gyp@3.8.0 and has a bin file directing to the wrong place.
setting environment variable solves this issue:

 set npm_config_node_gyp=path/to/../npm/node_modules/node-gyp/bin/node-gyp.js

This should be documented

NBSeven · 2019-06-04T10:10:16Z

Error: Cannot find module 'C:\Program Files\nodejs\node_modules\npm\node_modules\node_modules\node-gyp\bin\node-gyp.js'

node-v node@10.15.1
set npm_config_node_gyp='rightpath' this line dosen't work in powershell
cmd.exe does work

NBSeven · 2019-06-06T08:00:02Z

Error: Cannot find module 'C:\Program Files\nodejs\node_modules\npm\node_modules\node_modules\node-gyp\bin\node-gyp.js'

node-v node@10.15.1
set npm_config_node_gyp='rightpath' this line dosen't work in powershell
cmd.exe does work

Now i found ref and node-ffi can't be installed , node-gyp would rebuild them first but they were failed.Error message:
error MSB4019 :未找到导入的项目 "F:\Microsoft.Cpp.Default.props"。请确认声明中的路径正确，且磁盘上存在该文件。This is a problem about "path" too , just like 'wrong path to node-gyp bin'

bzoz · 2019-06-10T12:29:53Z

@ShaMan123 @NBSeven for whatever reason when calling node-gyp you end up running npm internal node-gyp script. That should not happen, so:

can you run where node-gyp and paste the results here?
can you share your PATH environment variable? Pasting the result of running echo %PATH% would be great.
do you remember maybe your "Node history"? Which version you installed, if you upgraded it, maybe the packages that you installed? There is definitely something off in your setups, knowing your upgrade path would be helpful to find the offending package.

Thanks!

NBSeven · 2019-06-10T12:48:04Z

@ShaMan123 @NBSeven for whatever reason when calling node-gyp you end up running npm internal node-gyp script. That should not happen, so:

can you run where node-gyp and paste the results here?

can you share your PATH environment variable? Pasting the result of running echo %PATH% would be great.

do you remember maybe your "Node history"? Which version you installed, if you upgraded it, maybe the packages that you installed? There is definitely something off in your setups, knowing your upgrade path would be helpful to find the offending package.

Thanks!

$ where node-gyp
C:\Program Files\nodejs\node_modules\npm\node_modules\npm-lifecycle\node-gyp-bin \node-gyp
C:\Program Files\nodejs\node_modules\npm\node_modules\npm-lifecycle\node-gyp-bin \node-gyp.cmd C:\Users\wangzhongxiang5\AppData\Roaming\npm\node-gyp C:\Users\wangzhongxiang5\AppData\Roaming\npm\node-gyp.cmd

C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0;C:\Program Files\Git\cmd;C:\Program Files\nodejs;C:\Program Files\TortoiseSVN\bin;C:\Users\wangzhongxiang5.windows-build-tools\python27;C:\Program Files\nodejs\node_modules\npm\node_modules\npm-lifecycle\node-gyp-bin;C:\Users\wangzhongxiang5\AppData\Roaming\npm\node_modules\windows-build-tools\node_modules.bin;C:\Users\wangzhongxiang5\AppData\Roaming\npm\node_modules.bin;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0;C:\Program Files\Git\cmd;C:\Program Files\nodejs;C:\Program Files\TortoiseSVN\bin;C:\Users\wangzhongxiang5\AppData\Local\Microsoft\WindowsApps;C:\Users\wangzhongxiang5\AppData\Roaming\npm;C:\Users\wangzhongxiang5\AppData\Local\Programs\Microsoft VS Code\bin
3.
$ node -v v10.15.1

bzoz · 2019-06-10T12:48:56Z

@NBSeven I see you have C:\Program Files\nodejs\node_modules\npm\node_modules\npm-lifecycle\node-gyp-bin in your PATH, it should not be there. Any idea how it was added there?

NBSeven · 2019-06-10T12:58:27Z

@bzoz I have no idea ....
I set mirror path about npm , npm config set registry https://registry.npm.taobao.org.
Then run npm i node-gyp -g

NBSeven · 2019-06-10T13:00:59Z

@bzoz I have no idea ....
I set mirror path about npm , npm config set registry https://registry.npm.taobao.org.
Then run npm i node-gyp -g
and i use nrm to manage my npm registry.

bzoz · 2019-06-10T13:02:26Z

ok, so can you try removing C:\Program Files\nodejs\node_modules\npm\node_modules\npm-lifecycle\node-gyp-bin from your PATH and test if that helps?

NBSeven · 2019-06-10T13:17:21Z

@bzoz
npm-cache_logs\2019-06-10T13_15_56_294Z-debug.log:

743 verbose stack Error: node-ffi@0.5.7 install: node-gyp rebuild
743 verbose stack Exit status 1
743 verbose stack at EventEmitter. (C:\Program Files\nodejs\node_modules\npm\node_modules\npm-lifecycle\index.js:301:16)
743 verbose stack at EventEmitter.emit (events.js:189:13)
743 verbose stack at ChildProcess. (C:\Program Files\nodejs\node_modules\npm\node_modules\npm-lifecycle\lib\spawn.js:55:14)
743 verbose stack at ChildProcess.emit (events.js:189:13)
743 verbose stack at maybeClose (internal/child_process.js:970:16)
743 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:259:5)
744 verbose pkgid node-ffi@0.5.7
745 verbose cwd F:\test\hello-world
746 verbose Windows_NT 10.0.16299
747 verbose argv "C:\Program Files\nodejs\node.exe" "C:\Program Files\nodejs\node_modules\npm\bin\npm-cli.js" "i" "node-ffi"
748 verbose node v10.15.1
749 verbose npm v6.4.1
750 error code ELIFECYCLE
751 error errno 1
752 error node-ffi@0.5.7 install: node-gyp rebuild
752 error Exit status 1
753 error Failed at the node-ffi@0.5.7 install script.
753 error This is probably not a problem with npm. There is likely additional logging output above.
754 verbose exit [ 1, true ]

bzoz · 2019-06-10T13:49:57Z

Is that the complete log? Can you run node-gyp rebuild --verbose and paste console output?

ShaMan123 · 2019-06-11T04:35:21Z

where node-gyp


Your environment has been set up for using Node.js 8.16.0 (x64) and npm.

C:\Users\DELL>where node-gyp
C:\Users\DELL\AppData\Roaming\npm\node-gyp
C:\Users\DELL\AppData\Roaming\npm\node-gyp.cmd
C:\Users\DELL\AppData\Roaming\npm\node_modules\npm\node_modules\npm-lifecycle\node-gyp-bin\node-gyp
C:\Users\DELL\AppData\Roaming\npm\node_modules\npm\node_modules\npm-lifecycle\node-gyp-bin\node-gyp.cmd

%PATH%


C:\Users\DELL>echo %PATH%
C:\Users\DELL\AppData\Roaming\npm;
C:\Program Files\nodejs\;
C:\Program Files\Microsoft MPI\Bin\;
C:\Program Files (x86)\Intel\iCLS Client\;
C:\Program Files\Intel\iCLS Client\;C:\WINDOWS\system32;
C:\WINDOWS;C:\WINDOWS\System32\Wbem;
C:\WINDOWS\System32\WindowsPowerShell\v1.0\;
C:\Program Files (x86)\Intel\Intel(R) Management Engine Components\DAL;
C:\Program Files\Intel\Intel(R) Management Engine Components\DAL;
C:\Program Files (x86)\Intel\Intel(R) Management Engine Components\IPT;
C:\Program Files\Intel\Intel(R) Management Engine Components\IPT;
C:\Program Files\dotnet\;
C:\Program Files\Microsoft SQL Server\130\Tools\Binn\;
C:\ProgramData\chocolatey\bin;
C:\Program Files (x86)\Google\Cloud SDK\google-cloud-sdk\bin;
C:\WINDOWS\System32\OpenSSH\;
C:\Program Files\Java\jdk1.8.0_172\bin;
C:\Program Files\Git\cmd;
C:\Program Files (x86)\Yarn\bin\;
C:\Program Files\nodejs\;
C:\Users\DELL\.windows-build-tools\python27\;
C:\Users\DELL\AppData\Roaming\npm\node_modules\npm\node_modules\npm-lifecycle\node-gyp-bin;
C:\Users\DELL\AppData\Roaming\npm\node_modules\windows-build-tools\node_modules\.bin;
C:\Users\DELL\AppData\Roaming\npm\node_modules\.bin;
C:\Program Files\Microsoft MPI\Bin\;
C:\Program Files (x86)\Intel\iCLS Client\;
C:\Program Files\Intel\iCLS Client\;
C:\WINDOWS\system32;
C:\WINDOWS;
C:\WINDOWS\System32\Wbem;
C:\WINDOWS\System32\WindowsPowerShell\v1.0\;
C:\Program Files (x86)\Intel\Intel(R) Management Engine Components\DAL;
C:\Program Files\Intel\Intel(R) Management Engine Components\DAL;
C:\Program Files (x86)\Intel\Intel(R) Management Engine Components\IPT;
C:\Program Files\Intel\Intel(R) Management Engine Components\IPT;
C:\Program Files\dotnet\;
C:\Program Files\Microsoft SQL Server\130\Tools\Binn\;
C:\ProgramData\chocolatey\bin;
C:\Program Files (x86)\Google\Cloud SDK\google-cloud-sdk\bin;
C:\WINDOWS\System32\OpenSSH\;
C:\Program Files\Java\jdk1.8.0_172\bin;
C:\Program Files\Git\cmd;
C:\Program Files\nodejs\;
C:\Program Files (x86)\Yarn\bin\;
C:\Users\DELL\AppData\Local\Programs\Python\Python36-32\Scripts\;
C:\Users\DELL\AppData\Local\Programs\Python\Python36-32\;
C:\Users\DELL\AppData\Local\Microsoft\WindowsApps;
C:\Users\DELL\AppData\Local\GitHubDesktop\bin;
C:\Users\DELL\AppData\Local\Yarn\bin;
C:\Users\DELL\AppData\Roaming\npm

bzoz · 2019-06-12T09:45:23Z

Thanks!

bzoz · 2019-06-12T10:16:19Z

@ShaMan123 in your PATH variable you have

C:\Users\DELL\AppData\Roaming\npm\node_modules\npm\node_modules\npm-lifecycle\node-gyp-bin;
C:\Users\DELL\AppData\Roaming\npm\node_modules\windows-build-tools\node_modules\.bin;

those probably should not be there and are causing the issues, especially the first one. Do you have any idea how those where added to your PATH variable?

NBSeven · 2019-06-12T10:32:46Z

node-gyp rebuild --verbose

PS F:\test\eleDemo> cd .\node-ffi\
PS F:\test\eleDemo\node-ffi> node-gyp rebuild --verbose
gyp info it worked if it ends with ok
gyp verb cli [ 'C:\\Program Files\\nodejs\\node.exe',
gyp verb cli   'C:\\Users\\wangzhongxiang5\\AppData\\Roaming\\npm\\node_modules\\node-gyp\\bin\\node-gyp.js',
gyp verb cli   'rebuild',
gyp verb cli   '--verbose' ]
gyp info using node-gyp@4.0.0
gyp info using node@10.15.1 | win32 | x64
gyp verb command rebuild []
gyp verb command clean []
gyp verb clean removing "build" directory
gyp verb command configure []
gyp verb check python checking for Python executable "python2" in the PATH
gyp verb `which` failed Error: not found: python2
gyp verb `which` failed     at getNotFoundError (C:\Users\wangzhongxiang5\AppData\Roaming\npm\node_modules\node-gyp\node_modules\which\which.js:13:12)
gyp verb `which` failed     at F (C:\Users\wangzhongxiang5\AppData\Roaming\npm\node_modules\node-gyp\node_modules\which\which.js:68:19)
gyp verb `which` failed     at E (C:\Users\wangzhongxiang5\AppData\Roaming\npm\node_modules\node-gyp\node_modules\which\which.js:80:29)
gyp verb `which` failed     at C:\Users\wangzhongxiang5\AppData\Roaming\npm\node_modules\node-gyp\node_modules\which\which.js:89:16
gyp verb `which` failed     at C:\Users\wangzhongxiang5\AppData\Roaming\npm\node_modules\node-gyp\node_modules\isexe\index.js:42:5
gyp verb `which` failed     at C:\Users\wangzhongxiang5\AppData\Roaming\npm\node_modules\node-gyp\node_modules\isexe\windows.js:36:5
gyp verb `which` failed     at FSReqWrap.oncomplete (fs.js:154:21)
gyp verb `which` failed  python2 { Error: not found: python2
gyp verb `which` failed     at getNotFoundError (C:\Users\wangzhongxiang5\AppData\Roaming\npm\node_modules\node-gyp\node_modules\which\which.js:13:12)
gyp verb `which` failed     at F (C:\Users\wangzhongxiang5\AppData\Roaming\npm\node_modules\node-gyp\node_modules\which\which.js:68:19)
gyp verb `which` failed     at E (C:\Users\wangzhongxiang5\AppData\Roaming\npm\node_modules\node-gyp\node_modules\which\which.js:80:29)
gyp verb `which` failed     at C:\Users\wangzhongxiang5\AppData\Roaming\npm\node_modules\node-gyp\node_modules\which\which.js:89:16
gyp verb `which` failed     at C:\Users\wangzhongxiang5\AppData\Roaming\npm\node_modules\node-gyp\node_modules\isexe\index.js:42:5
gyp verb `which` failed     at C:\Users\wangzhongxiang5\AppData\Roaming\npm\node_modules\node-gyp\node_modules\isexe\windows.js:36:5
gyp verb `which` failed     at FSReqWrap.oncomplete (fs.js:154:21)
gyp verb `which` failed   stack:
gyp verb `which` failed    'Error: not found: python2\n    at getNotFoundError (C:\\Users\\wangzhongxiang5\\AppData\\Roaming\\npm\\node_modules\\node-gyp\\node_modules\\which\\which.js:13:12)\n    at F (C:\\Users\\wangzhongxiang5\\AppData\\Roaming\\npm\\node_modules\\node-gyp\\node_modules\\which\\which.js:68:19)\n    at E (C:\\Users\\wangzhongxiang5\\AppData\\Roaming\\npm\\node_modules\\node-gyp\\node_modules\\which\\which.js:80:29)\n    at C:\\Users\\wangzhongxiang5\\AppData\\Roaming\\npm\\node_modules\\node-gyp\\node_modules\\which\\which.js:89:16\n    at C:\\Users\\wangzhongxiang5\\AppData\\Roaming\\npm\\node_modules\\node-gyp\\node_modules\\isexe\\index.js:42:5\n    at C:\\Users\\wangzhongxiang5\\AppData\\Roaming\\npm\\node_modules\\node-gyp\\node_modules\\isexe\\windows.js:36:5\n    at FSReqWrap.oncomplete (fs.js:154:21)',
gyp verb `which` failed   code: 'ENOENT' }
gyp verb check python checking for Python executable "python" in the PATH
gyp verb `which` succeeded python C:\Users\wangzhongxiang5\.windows-build-tools\python27\python.EXE
gyp verb check python version `C:\Users\wangzhongxiang5\.windows-build-tools\python27\python.EXE -c "import sys; print("2.7.15
gyp verb check python version .%s.%s" % sys.version_info[:3]);"` returned: %j
gyp verb get node dir no --target version specified, falling back to host node version: 10.15.1
gyp verb command install [ '10.15.1' ]
gyp verb install input version string "10.15.1"
gyp verb install installing version: 10.15.1
gyp verb install --ensure was passed, so won't reinstall if already installed
gyp verb install version is already installed, need to check "installVersion"
gyp verb got "installVersion" 9
gyp verb needs "installVersion" 9
gyp verb install version is good
gyp verb get node dir target node version installed: 10.15.1
gyp verb build dir attempting to create "build" dir: F:\test\eleDemo\node-ffi\build
gyp verb build dir "build" dir needed to be created? F:\test\eleDemo\node-ffi\build
gyp verb find vs2017 Found installation at: C:\Program Files (x86)\Microsoft Visual Studio\2017\BuildTools
gyp verb find vs2017   - Found Microsoft.VisualStudio.Component.Windows10SDK.17763
gyp verb find vs2017   - Found Microsoft.VisualStudio.Component.VC.Tools.x86.x64
gyp verb find vs2017   - Found Microsoft.VisualStudio.VC.MSBuild.Base
gyp verb find vs2017   - Using this installation with Windows 10 SDK
gyp verb find vs2017 using installation: C:\Program Files (x86)\Microsoft Visual Studio\2017\BuildTools
gyp verb build/config.gypi creating config file
gyp verb build/config.gypi writing out config file: F:\test\eleDemo\node-ffi\build\config.gypi
gyp verb config.gypi checking for gypi file: F:\test\eleDemo\node-ffi\config.gypi
gyp verb common.gypi checking for gypi file: F:\test\eleDemo\node-ffi\common.gypi
gyp verb gyp gyp format was not specified; forcing "msvs"
gyp info spawn C:\Users\wangzhongxiang5\.windows-build-tools\python27\python.EXE
gyp info spawn args [ 'C:\\Users\\wangzhongxiang5\\AppData\\Roaming\\npm\\node_modules\\node-gyp\\gyp\\gyp_main.py',
gyp info spawn args   'binding.gyp',
gyp info spawn args   '-f',
gyp info spawn args   'msvs',
gyp info spawn args   '-G',
gyp info spawn args   'msvs_version=2015',
gyp info spawn args   '-I',
gyp info spawn args   'F:\\test\\eleDemo\\node-ffi\\build\\config.gypi',
gyp info spawn args   '-I',
gyp info spawn args   'C:\\Users\\wangzhongxiang5\\AppData\\Roaming\\npm\\node_modules\\node-gyp\\addon.gypi',
gyp info spawn args   '-I',
gyp info spawn args   'C:\\Users\\wangzhongxiang5\\.node-gyp\\10.15.1\\include\\node\\common.gypi',
gyp info spawn args   '-Dlibrary=shared_library',
gyp info spawn args   '-Dvisibility=default',
gyp info spawn args   '-Dnode_root_dir=C:\\Users\\wangzhongxiang5\\.node-gyp\\10.15.1',
gyp info spawn args   '-Dnode_gyp_dir=C:\\Users\\wangzhongxiang5\\AppData\\Roaming\\npm\\node_modules\\node-gyp',
gyp info spawn args   '-Dnode_lib_file=C:\\Users\\wangzhongxiang5\\.node-gyp\\10.15.1\\<(target_arch)\\node.lib',
gyp info spawn args   '-Dmodule_root_dir=F:\\test\\eleDemo\\node-ffi',
gyp info spawn args   '-Dnode_engine=v8',
gyp info spawn args   '--depth=.',
gyp info spawn args   '--no-parallel',
gyp info spawn args   '--generator-output',
gyp info spawn args   'F:\\test\\eleDemo\\node-ffi\\build',
gyp info spawn args   '-Goutput_dir=.' ]
gyp verb command build []
gyp verb build type Release
gyp verb architecture x64
gyp verb node dev dir C:\Users\wangzhongxiang5\.node-gyp\10.15.1
gyp verb found first Solution file build/binding.sln
gyp verb using MSBuild: C:\Program Files (x86)\Microsoft Visual Studio\2017\BuildTools\MSBuild\15.0\Bin\MSBuild.exe
gyp info spawn C:\Program Files (x86)\Microsoft Visual Studio\2017\BuildTools\MSBuild\15.0\Bin\MSBuild.exe
gyp info spawn args [ 'build/binding.sln',
gyp info spawn args   '/nologo',
gyp info spawn args   '/p:Configuration=Release;Platform=x64' ]
在此解决方案中一次生成一个项目。若要启用并行生成，请添加“/m”开关。
生成启动时间为 2019/6/12 18:28:45。
节点 1 上的项目“F:\test\eleDemo\node-ffi\build\binding.sln”(默认目标)。
ValidateSolutionConfiguration:
  正在生成解决方案配置“Release|x64”。
项目“F:\test\eleDemo\node-ffi\build\binding.sln”(1)正在节点 1 上生成“F:\test\eleDemo\node-ffi\build\deps\libffi\ffi.vcxproj”(2) (默认目标)。
PrepareForBuild:
  正在创建目录“Release\obj\ffi\”。
  正在创建目录“F:\test\eleDemo\node-ffi\build\Release\”。
  正在创建目录“Release\obj\ffi\ffi.tlog\”。
InitializeBuildStatus:
  正在创建“Release\obj\ffi\ffi.tlog\unsuccessfulbuild”，因为已指定“AlwaysCreate”。
_assembler:
  Building assembly file ..\..\..\deps\libffi\src\x86\win64.asm
  cmd.exe /Q /D /C "C:\Users\wangzhongxiang5\AppData\Local\Temp\tmp98808d49d62849598369b5a976332b57.cmd"
  call ml64 "/nologo" "/c" "/FoRelease\obj\ffi\win64.obj" "..\..\..\deps\libffi\src\x86\win64.asm"
   Assembling: ..\..\..\deps\libffi\src\x86\win64.asm
ClCompile:
  C:\Program Files (x86)\Microsoft Visual Studio\2017\BuildTools\VC\Tools\MSVC\14.16.27023\bin\HostX64\x64\CL.exe /c /I"C:\Users\wangzhongxiang5\.node-gyp\10.15.1\include\node" /I"C:\Users\wangzhongxiang5\.no
  de-gyp\10.15.1\src" /I"C:\Users\wangzhongxiang5\.node-gyp\10.15.1\deps\openssl\config" /I"C:\Users\wangzhongxiang5\.node-gyp\10.15.1\deps\openssl\openssl\include" /I"C:\Users\wangzhongxiang5\.node-gyp\10.15
  .1\deps\uv\include" /I"C:\Users\wangzhongxiang5\.node-gyp\10.15.1\deps\zlib" /I"C:\Users\wangzhongxiang5\.node-gyp\10.15.1\deps\v8\include" /I..\..\..\deps\libffi\include /I..\..\..\deps\libffi\config\win\x
  64 /Z7 /nologo /W3 /WX- /diagnostics:classic /MP /Ox /Ob2 /Oi /Ot /Oy /GL /D NODE_GYP_MODULE_NAME=ffi /D USING_UV_SHARED=1 /D USING_V8_SHARED=1 /D V8_DEPRECATION_WARNINGS=1 /D WIN32 /D _CRT_SECURE_NO_DEPREC
  ATE /D _CRT_NONSTDC_NO_DEPRECATE /D _HAS_EXCEPTIONS=0 /D PIC /D FFI_BUILDING /D HAVE_CONFIG_H /D NDEBUG /GF /Gm- /MT /GS /Gy /fp:precise /Zc:wchar_t /Zc:forScope /Zc:inline /GR- /Fo"Release\obj\ffi\\" /Fd"R
  elease\obj\ffi\ffi.pdb" /Gd /TC /wd4351 /wd4355 /wd4800 /wd4251 /wd4275 /wd4244 /wd4267 /FC /errorReport:queue ..\..\..\deps\libffi\src\prep_cif.c ..\..\..\deps\libffi\src\types.c ..\..\..\deps\libffi\src\r
  aw_api.c ..\..\..\deps\libffi\src\java_raw_api.c ..\..\..\deps\libffi\src\closures.c ..\..\..\deps\libffi\src\x86\ffi.c
  prep_cif.c
  types.c
  raw_api.c
  java_raw_api.c
  closures.c
  ffi.c
  C:\Program Files (x86)\Microsoft Visual Studio\2017\BuildTools\VC\Tools\MSVC\14.16.27023\bin\HostX64\x64\CL.exe /c /I"C:\Users\wangzhongxiang5\.node-gyp\10.15.1\include\node" /I"C:\Users\wangzhongxiang5\.no
  de-gyp\10.15.1\src" /I"C:\Users\wangzhongxiang5\.node-gyp\10.15.1\deps\openssl\config" /I"C:\Users\wangzhongxiang5\.node-gyp\10.15.1\deps\openssl\openssl\include" /I"C:\Users\wangzhongxiang5\.node-gyp\10.15
  .1\deps\uv\include" /I"C:\Users\wangzhongxiang5\.node-gyp\10.15.1\deps\zlib" /I"C:\Users\wangzhongxiang5\.node-gyp\10.15.1\deps\v8\include" /I..\..\..\deps\libffi\include /I..\..\..\deps\libffi\config\win\x
  64 /Z7 /nologo /W3 /WX- /diagnostics:classic /MP /Ox /Ob2 /Oi /Ot /Oy /GL /D NODE_GYP_MODULE_NAME=ffi /D USING_UV_SHARED=1 /D USING_V8_SHARED=1 /D V8_DEPRECATION_WARNINGS=1 /D WIN32 /D _CRT_SECURE_NO_DEPREC
  ATE /D _CRT_NONSTDC_NO_DEPRECATE /D _HAS_EXCEPTIONS=0 /D PIC /D FFI_BUILDING /D HAVE_CONFIG_H /D NDEBUG /GF /Gm- /MT /GS /Gy /fp:precise /Zc:wchar_t /Zc:forScope /Zc:inline /GR- /Fo"Release\obj\ffi\\" /Fd"R
  elease\obj\ffi\ffi.pdb" /Gd /TP /wd4351 /wd4355 /wd4800 /wd4251 /wd4275 /wd4244 /wd4267 /FC /errorReport:queue "C:\Users\wangzhongxiang5\AppData\Roaming\npm\node_modules\node-gyp\src\win_delay_load_hook.cc"
  win_delay_load_hook.cc
Lib:
  C:\Program Files (x86)\Microsoft Visual Studio\2017\BuildTools\VC\Tools\MSVC\14.16.27023\bin\HostX64\x64\Lib.exe /OUT:"F:\test\eleDemo\node-ffi\build\Release\libffi.lib" /NOLOGO /MACHINE:X64 /LTCG:INCREMENT
  AL Release\obj\ffi\win64.obj
  Release\obj\ffi\prep_cif.obj
  Release\obj\ffi\types.obj
  Release\obj\ffi\raw_api.obj
  Release\obj\ffi\java_raw_api.obj
  Release\obj\ffi\closures.obj
  Release\obj\ffi\ffi.obj
  Release\obj\ffi\win_delay_load_hook.obj
  ffi.vcxproj -> F:\test\eleDemo\node-ffi\build\Release\\libffi.lib
FinalizeBuildStatus:
  正在删除文件“Release\obj\ffi\ffi.tlog\unsuccessfulbuild”。
  正在对“Release\obj\ffi\ffi.tlog\ffi.lastbuildstate”执行 Touch 任务。
已完成生成项目“F:\test\eleDemo\node-ffi\build\deps\libffi\ffi.vcxproj”(默认目标)的操作。

项目“F:\test\eleDemo\node-ffi\build\binding.sln”(1)正在节点 1 上生成“F:\test\eleDemo\node-ffi\build\ffi_bindings.vcxproj.metaproj”(3) (默认目标)。
项目“F:\test\eleDemo\node-ffi\build\ffi_bindings.vcxproj.metaproj”(3)正在节点 1 上生成“F:\test\eleDemo\node-ffi\build\ffi_bindings.vcxproj”(4) (默认目标)。
PrepareForBuild:
  正在创建目录“Release\obj\ffi_bindings\”。
  正在创建目录“Release\obj\ffi_bindings\ffi_bindings.tlog\”。
InitializeBuildStatus:
  正在创建“Release\obj\ffi_bindings\ffi_bindings.tlog\unsuccessfulbuild”，因为已指定“AlwaysCreate”。
ClCompile:
  C:\Program Files (x86)\Microsoft Visual Studio\2017\BuildTools\VC\Tools\MSVC\14.16.27023\bin\HostX64\x64\CL.exe /c /I"C:\Users\wangzhongxiang5\.node-gyp\10.15.1\include\node" /I"C:\Users\wangzhongxiang5\.no
  de-gyp\10.15.1\src" /I"C:\Users\wangzhongxiang5\.node-gyp\10.15.1\deps\openssl\config" /I"C:\Users\wangzhongxiang5\.node-gyp\10.15.1\deps\openssl\openssl\include" /I"C:\Users\wangzhongxiang5\.node-gyp\10.15
  .1\deps\uv\include" /I"C:\Users\wangzhongxiang5\.node-gyp\10.15.1\deps\zlib" /I"C:\Users\wangzhongxiang5\.node-gyp\10.15.1\deps\v8\include" /I..\..\node_modules\nan /I..\deps\libffi\include /I..\deps\libffi
  \config\win\x64 /Z7 /nologo /W3 /WX- /diagnostics:classic /MP /Ox /Ob2 /Oi /Ot /Oy /GL /D NODE_GYP_MODULE_NAME=ffi_bindings /D USING_UV_SHARED=1 /D USING_V8_SHARED=1 /D V8_DEPRECATION_WARNINGS=1 /D WIN32 /D
   _CRT_SECURE_NO_DEPRECATE /D _CRT_NONSTDC_NO_DEPRECATE /D _HAS_EXCEPTIONS=0 /D BUILDING_NODE_EXTENSION /D _WINDLL /GF /Gm- /MT /GS /Gy /fp:precise /Zc:wchar_t /Zc:forScope /Zc:inline /GR- /Fo"Release\obj\ff
  i_bindings\\" /Fd"Release\obj\ffi_bindings\vc141.pdb" /Gd /TP /wd4351 /wd4355 /wd4800 /wd4251 /wd4275 /wd4244 /wd4267 /FC /errorReport:queue ..\src\ffi.cc ..\src\callback_info.cc ..\src\threaded_callback_in
  vokation.cc "..\src\win32-dlfcn.cc" "C:\Users\wangzhongxiang5\AppData\Roaming\npm\node_modules\node-gyp\src\win_delay_load_hook.cc"
  ffi.cc
  callback_info.cc
  threaded_callback_invokation.cc
  win32-dlfcn.cc
  win_delay_load_hook.cc
f:\test\eledemo\node-ffi\src\callback_info.cc(63): warning C4996: 'Nan::Callback::Call': 被声明为已否决 [F:\test\eleDemo\node-ffi\build\ffi_bindings.vcxproj]
  f:\test\eledemo\node_modules\nan\nan.h(1740): note: 参见“Nan::Callback::Call”的声明
f:\test\eledemo\node-ffi\src\callback_info.cc(73): warning C4996: 'Nan::Callback::Call': 被声明为已否决 [F:\test\eleDemo\node-ffi\build\ffi_bindings.vcxproj]
  f:\test\eledemo\node_modules\nan\nan.h(1740): note: 参见“Nan::Callback::Call”的声明
f:\test\eledemo\node-ffi\src\callback_info.cc(78): warning C4996: 'Nan::Callback::Call': 被声明为已否决 [F:\test\eleDemo\node-ffi\build\ffi_bindings.vcxproj]
  f:\test\eledemo\node_modules\nan\nan.h(1740): note: 参见“Nan::Callback::Call”的声明
f:\test\eledemo\node-ffi\src\callback_info.cc(112): warning C4996: 'v8::Value::ToObject': 被声明为已否决 [F:\test\eleDemo\node-ffi\build\ffi_bindings.vcxproj]
  c:\users\wangzhongxiang5\.node-gyp\10.15.1\include\node\v8.h(10046): note: 参见“v8::Value::ToObject”的声明
f:\test\eledemo\node-ffi\src\callback_info.cc(113): warning C4996: 'v8::Value::Int32Value': 被声明为已否决 [F:\test\eleDemo\node-ffi\build\ffi_bindings.vcxproj]
  c:\users\wangzhongxiang5\.node-gyp\10.15.1\include\node\v8.h(2478): note: 参见“v8::Value::Int32Value”的声明
f:\test\eledemo\node-ffi\src\callback_info.cc(114): warning C4996: 'v8::Value::Int32Value': 被声明为已否决 [F:\test\eleDemo\node-ffi\build\ffi_bindings.vcxproj]
  c:\users\wangzhongxiang5\.node-gyp\10.15.1\include\node\v8.h(2478): note: 参见“v8::Value::Int32Value”的声明
f:\test\eledemo\node-ffi\src\ffi.cc(58): warning C4996: 'Nan::ForceSet': 被声明为已否决 [F:\test\eleDemo\node-ffi\build\ffi_bindings.vcxproj]
  f:\test\eledemo\node_modules\nan\nan_maybe_43_inl.h(117): note: 参见“Nan::ForceSet”的声明
f:\test\eledemo\node-ffi\src\ffi.cc(59): warning C4996: 'Nan::ForceSet': 被声明为已否决 [F:\test\eleDemo\node-ffi\build\ffi_bindings.vcxproj]
  f:\test\eledemo\node_modules\nan\nan_maybe_43_inl.h(117): note: 参见“Nan::ForceSet”的声明
f:\test\eledemo\node-ffi\src\ffi.cc(60): warning C4996: 'Nan::ForceSet': 被声明为已否决 [F:\test\eleDemo\node-ffi\build\ffi_bindings.vcxproj]
  f:\test\eledemo\node_modules\nan\nan_maybe_43_inl.h(117): note: 参见“Nan::ForceSet”的声明
f:\test\eledemo\node-ffi\src\ffi.cc(63): warning C4996: 'Nan::ForceSet': 被声明为已否决 [F:\test\eleDemo\node-ffi\build\ffi_bindings.vcxproj]
  f:\test\eledemo\node_modules\nan\nan_maybe_43_inl.h(117): note: 参见“Nan::ForceSet”的声明
f:\test\eledemo\node-ffi\src\ffi.cc(64): warning C4996: 'Nan::ForceSet': 被声明为已否决 [F:\test\eleDemo\node-ffi\build\ffi_bindings.vcxproj]
  f:\test\eledemo\node_modules\nan\nan_maybe_43_inl.h(117): note: 参见“Nan::ForceSet”的声明
f:\test\eledemo\node-ffi\src\ffi.cc(65): warning C4996: 'Nan::ForceSet': 被声明为已否决 [F:\test\eleDemo\node-ffi\build\ffi_bindings.vcxproj]
  f:\test\eledemo\node_modules\nan\nan_maybe_43_inl.h(117): note: 参见“Nan::ForceSet”的声明
f:\test\eledemo\node-ffi\src\ffi.cc(78): warning C4996: 'Nan::ForceSet': 被声明为已否决 [F:\test\eleDemo\node-ffi\build\ffi_bindings.vcxproj]
  f:\test\eledemo\node_modules\nan\nan_maybe_43_inl.h(117): note: 参见“Nan::ForceSet”的声明
f:\test\eledemo\node-ffi\src\ffi.cc(88): warning C4996: 'Nan::ForceSet': 被声明为已否决 [F:\test\eleDemo\node-ffi\build\ffi_bindings.vcxproj]
  f:\test\eledemo\node_modules\nan\nan_maybe_43_inl.h(117): note: 参见“Nan::ForceSet”的声明
f:\test\eledemo\node-ffi\src\ffi.cc(91): warning C4996: 'Nan::ForceSet': 被声明为已否决 [F:\test\eleDemo\node-ffi\build\ffi_bindings.vcxproj]
  f:\test\eledemo\node_modules\nan\nan_maybe_43_inl.h(117): note: 参见“Nan::ForceSet”的声明
f:\test\eledemo\node-ffi\src\ffi.cc(94): warning C4996: 'Nan::ForceSet': 被声明为已否决 [F:\test\eleDemo\node-ffi\build\ffi_bindings.vcxproj]
  f:\test\eledemo\node_modules\nan\nan_maybe_43_inl.h(117): note: 参见“Nan::ForceSet”的声明
f:\test\eledemo\node-ffi\src\ffi.cc(97): warning C4996: 'Nan::ForceSet': 被声明为已否决 [F:\test\eleDemo\node-ffi\build\ffi_bindings.vcxproj]
  f:\test\eledemo\node_modules\nan\nan_maybe_43_inl.h(117): note: 参见“Nan::ForceSet”的声明
f:\test\eledemo\node-ffi\src\ffi.cc(111): warning C4996: 'Nan::ForceSet': 被声明为已否决 [F:\test\eleDemo\node-ffi\build\ffi_bindings.vcxproj]
  f:\test\eledemo\node_modules\nan\nan_maybe_43_inl.h(117): note: 参见“Nan::ForceSet”的声明
f:\test\eledemo\node-ffi\src\ffi.cc(114): warning C4996: 'Nan::ForceSet': 被声明为已否决 [F:\test\eleDemo\node-ffi\build\ffi_bindings.vcxproj]
  f:\test\eledemo\node_modules\nan\nan_maybe_43_inl.h(117): note: 参见“Nan::ForceSet”的声明
f:\test\eledemo\node-ffi\src\ffi.cc(123): warning C4996: 'Nan::ForceSet': 被声明为已否决 [F:\test\eleDemo\node-ffi\build\ffi_bindings.vcxproj]
  f:\test\eledemo\node_modules\nan\nan_maybe_43_inl.h(117): note: 参见“Nan::ForceSet”的声明
f:\test\eledemo\node-ffi\src\ffi.cc(124): warning C4996: 'Nan::ForceSet': 被声明为已否决 [F:\test\eleDemo\node-ffi\build\ffi_bindings.vcxproj]
  f:\test\eledemo\node_modules\nan\nan_maybe_43_inl.h(117): note: 参见“Nan::ForceSet”的声明
f:\test\eledemo\node-ffi\src\ffi.cc(125): warning C4996: 'Nan::ForceSet': 被声明为已否决 [F:\test\eleDemo\node-ffi\build\ffi_bindings.vcxproj]
  f:\test\eledemo\node_modules\nan\nan_maybe_43_inl.h(117): note: 参见“Nan::ForceSet”的声明
f:\test\eledemo\node-ffi\src\ffi.cc(126): warning C4996: 'Nan::ForceSet': 被声明为已否决 [F:\test\eleDemo\node-ffi\build\ffi_bindings.vcxproj]
  f:\test\eledemo\node_modules\nan\nan_maybe_43_inl.h(117): note: 参见“Nan::ForceSet”的声明
f:\test\eledemo\node-ffi\src\ffi.cc(132): warning C4996: 'Nan::ForceSet': 被声明为已否决 [F:\test\eleDemo\node-ffi\build\ffi_bindings.vcxproj]
  f:\test\eledemo\node_modules\nan\nan_maybe_43_inl.h(117): note: 参见“Nan::ForceSet”的声明
f:\test\eledemo\node-ffi\src\ffi.cc(190): warning C4996: 'v8::Value::Uint32Value': 被声明为已否决 [F:\test\eleDemo\node-ffi\build\ffi_bindings.vcxproj]
  c:\users\wangzhongxiang5\.node-gyp\10.15.1\include\node\v8.h(2477): note: 参见“v8::Value::Uint32Value”的声明
f:\test\eledemo\node-ffi\src\ffi.cc(191): warning C4996: 'v8::Value::ToObject': 被声明为已否决 [F:\test\eleDemo\node-ffi\build\ffi_bindings.vcxproj]
  c:\users\wangzhongxiang5\.node-gyp\10.15.1\include\node\v8.h(10046): note: 参见“v8::Value::ToObject”的声明
f:\test\eledemo\node-ffi\src\ffi.cc(192): warning C4996: 'v8::Value::ToObject': 被声明为已否决 [F:\test\eleDemo\node-ffi\build\ffi_bindings.vcxproj]
  c:\users\wangzhongxiang5\.node-gyp\10.15.1\include\node\v8.h(10046): note: 参见“v8::Value::ToObject”的声明
f:\test\eledemo\node-ffi\src\ffi.cc(193): warning C4996: 'v8::Value::Uint32Value': 被声明为已否决 [F:\test\eleDemo\node-ffi\build\ffi_bindings.vcxproj]
  c:\users\wangzhongxiang5\.node-gyp\10.15.1\include\node\v8.h(2477): note: 参见“v8::Value::Uint32Value”的声明
f:\test\eledemo\node-ffi\src\ffi.cc(234): warning C4996: 'v8::Value::Uint32Value': 被声明为已否决 [F:\test\eleDemo\node-ffi\build\ffi_bindings.vcxproj]
  c:\users\wangzhongxiang5\.node-gyp\10.15.1\include\node\v8.h(2477): note: 参见“v8::Value::Uint32Value”的声明
f:\test\eledemo\node-ffi\src\ffi.cc(235): warning C4996: 'v8::Value::Uint32Value': 被声明为已否决 [F:\test\eleDemo\node-ffi\build\ffi_bindings.vcxproj]
  c:\users\wangzhongxiang5\.node-gyp\10.15.1\include\node\v8.h(2477): note: 参见“v8::Value::Uint32Value”的声明
f:\test\eledemo\node-ffi\src\ffi.cc(236): warning C4996: 'v8::Value::ToObject': 被声明为已否决 [F:\test\eleDemo\node-ffi\build\ffi_bindings.vcxproj]
  c:\users\wangzhongxiang5\.node-gyp\10.15.1\include\node\v8.h(10046): note: 参见“v8::Value::ToObject”的声明
f:\test\eledemo\node-ffi\src\ffi.cc(237): warning C4996: 'v8::Value::ToObject': 被声明为已否决 [F:\test\eleDemo\node-ffi\build\ffi_bindings.vcxproj]
  c:\users\wangzhongxiang5\.node-gyp\10.15.1\include\node\v8.h(10046): note: 参见“v8::Value::ToObject”的声明
f:\test\eledemo\node-ffi\src\ffi.cc(238): warning C4996: 'v8::Value::Uint32Value': 被声明为已否决 [F:\test\eleDemo\node-ffi\build\ffi_bindings.vcxproj]
  c:\users\wangzhongxiang5\.node-gyp\10.15.1\include\node\v8.h(2477): note: 参见“v8::Value::Uint32Value”的声明
f:\test\eledemo\node-ffi\src\ffi.cc(265): warning C4996: 'v8::Value::ToObject': 被声明为已否决 [F:\test\eleDemo\node-ffi\build\ffi_bindings.vcxproj]
  c:\users\wangzhongxiang5\.node-gyp\10.15.1\include\node\v8.h(10046): note: 参见“v8::Value::ToObject”的声明
f:\test\eledemo\node-ffi\src\ffi.cc(266): warning C4996: 'v8::Value::ToObject': 被声明为已否决 [F:\test\eleDemo\node-ffi\build\ffi_bindings.vcxproj]
  c:\users\wangzhongxiang5\.node-gyp\10.15.1\include\node\v8.h(10046): note: 参见“v8::Value::ToObject”的声明
f:\test\eledemo\node-ffi\src\ffi.cc(267): warning C4996: 'v8::Value::ToObject': 被声明为已否决 [F:\test\eleDemo\node-ffi\build\ffi_bindings.vcxproj]
  c:\users\wangzhongxiang5\.node-gyp\10.15.1\include\node\v8.h(10046): note: 参见“v8::Value::ToObject”的声明
f:\test\eledemo\node-ffi\src\ffi.cc(268): warning C4996: 'v8::Value::ToObject': 被声明为已否决 [F:\test\eleDemo\node-ffi\build\ffi_bindings.vcxproj]
  c:\users\wangzhongxiang5\.node-gyp\10.15.1\include\node\v8.h(10046): note: 参见“v8::Value::ToObject”的声明
f:\test\eledemo\node-ffi\src\ffi.cc(307): warning C4996: 'v8::Value::ToObject': 被声明为已否决 [F:\test\eleDemo\node-ffi\build\ffi_bindings.vcxproj]
  c:\users\wangzhongxiang5\.node-gyp\10.15.1\include\node\v8.h(10046): note: 参见“v8::Value::ToObject”的声明
f:\test\eledemo\node-ffi\src\ffi.cc(308): warning C4996: 'v8::Value::ToObject': 被声明为已否决 [F:\test\eleDemo\node-ffi\build\ffi_bindings.vcxproj]
  c:\users\wangzhongxiang5\.node-gyp\10.15.1\include\node\v8.h(10046): note: 参见“v8::Value::ToObject”的声明
f:\test\eledemo\node-ffi\src\ffi.cc(309): warning C4996: 'v8::Value::ToObject': 被声明为已否决 [F:\test\eleDemo\node-ffi\build\ffi_bindings.vcxproj]
  c:\users\wangzhongxiang5\.node-gyp\10.15.1\include\node\v8.h(10046): note: 参见“v8::Value::ToObject”的声明
f:\test\eledemo\node-ffi\src\ffi.cc(310): warning C4996: 'v8::Value::ToObject': 被声明为已否决 [F:\test\eleDemo\node-ffi\build\ffi_bindings.vcxproj]
  c:\users\wangzhongxiang5\.node-gyp\10.15.1\include\node\v8.h(10046): note: 参见“v8::Value::ToObject”的声明
f:\test\eledemo\node-ffi\src\ffi.cc(367): warning C4996: 'Nan::Callback::Call': 被声明为已否决 [F:\test\eleDemo\node-ffi\build\ffi_bindings.vcxproj]
  f:\test\eledemo\node_modules\nan\nan.h(1740): note: 参见“Nan::Callback::Call”的声明
Link:
  C:\Program Files (x86)\Microsoft Visual Studio\2017\BuildTools\VC\Tools\MSVC\14.16.27023\bin\HostX64\x64\link.exe /ERRORREPORT:QUEUE /OUT:"F:\test\eleDemo\node-ffi\build\Release\ffi_bindings.node" /INCREMEN
  TAL:NO /NOLOGO kernel32.lib user32.lib gdi32.lib winspool.lib comdlg32.lib advapi32.lib shell32.lib ole32.lib oleaut32.lib uuid.lib odbc32.lib DelayImp.lib "C:\Users\wangzhongxiang5\.node-gyp\10.15.1\x64\no
  de.lib" Delayimp.lib /DELAYLOAD:iojs.exe /DELAYLOAD:node.exe /MANIFEST /MANIFESTUAC:"level='asInvoker' uiAccess='false'" /manifest:embed /DEBUG /PDB:"F:\test\eleDemo\node-ffi\build\Release\ffi_bindings.pdb"
   /MAP /MAPINFO:EXPORTS /OPT:REF /OPT:ICF /TLBID:1 /DYNAMICBASE /NXCOMPAT /MACHINE:X64 /ignore:4199 /LTCG:INCREMENTAL /DLL Release\obj\ffi_bindings\ffi.obj
  Release\obj\ffi_bindings\callback_info.obj
  Release\obj\ffi_bindings\threaded_callback_invokation.obj
  "Release\obj\ffi_bindings\win32-dlfcn.obj"
  Release\obj\ffi_bindings\win_delay_load_hook.obj
  "F:\test\eleDemo\node-ffi\build\Release\libffi.lib"
    正在创建库 F:\test\eleDemo\node-ffi\build\Release\ffi_bindings.lib 和对象 F:\test\eleDemo\node-ffi\build\Release\ffi_bindings.exp
  正在生成代码
  All 343 functions were compiled because no usable IPDB/IOBJ from previous compilation was found.
  已完成代码的生成
  ffi_bindings.vcxproj -> F:\test\eleDemo\node-ffi\build\Release\\ffi_bindings.node
FinalizeBuildStatus:
  正在删除文件“Release\obj\ffi_bindings\ffi_bindings.tlog\unsuccessfulbuild”。
  正在对“Release\obj\ffi_bindings\ffi_bindings.tlog\ffi_bindings.lastbuildstate”执行 Touch 任务。
已完成生成项目“F:\test\eleDemo\node-ffi\build\ffi_bindings.vcxproj”(默认目标)的操作。

已完成生成项目“F:\test\eleDemo\node-ffi\build\ffi_bindings.vcxproj.metaproj”(默认目标)的操作。

已完成生成项目“F:\test\eleDemo\node-ffi\build\binding.sln”(默认目标)的操作。


已成功生成。

“F:\test\eleDemo\node-ffi\build\binding.sln”(默认目标) (1) ->
“F:\test\eleDemo\node-ffi\build\ffi_bindings.vcxproj.metaproj”(默认目标) (3) ->
“F:\test\eleDemo\node-ffi\build\ffi_bindings.vcxproj”(默认目标) (4) ->
(ClCompile 目标) -> 
  f:\test\eledemo\node-ffi\src\callback_info.cc(63): warning C4996: 'Nan::Callback::Call': 被声明为已否决 [F:\test\eleDemo\node-ffi\build\ffi_bindings.vcxproj]
  f:\test\eledemo\node-ffi\src\callback_info.cc(73): warning C4996: 'Nan::Callback::Call': 被声明为已否决 [F:\test\eleDemo\node-ffi\build\ffi_bindings.vcxproj]
  f:\test\eledemo\node-ffi\src\callback_info.cc(78): warning C4996: 'Nan::Callback::Call': 被声明为已否决 [F:\test\eleDemo\node-ffi\build\ffi_bindings.vcxproj]
  f:\test\eledemo\node-ffi\src\callback_info.cc(112): warning C4996: 'v8::Value::ToObject': 被声明为已否决 [F:\test\eleDemo\node-ffi\build\ffi_bindings.vcxproj]
  f:\test\eledemo\node-ffi\src\callback_info.cc(113): warning C4996: 'v8::Value::Int32Value': 被声明为已否决 [F:\test\eleDemo\node-ffi\build\ffi_bindings.vcxproj]
  f:\test\eledemo\node-ffi\src\callback_info.cc(114): warning C4996: 'v8::Value::Int32Value': 被声明为已否决 [F:\test\eleDemo\node-ffi\build\ffi_bindings.vcxproj]
  f:\test\eledemo\node-ffi\src\ffi.cc(58): warning C4996: 'Nan::ForceSet': 被声明为已否决 [F:\test\eleDemo\node-ffi\build\ffi_bindings.vcxproj]
  f:\test\eledemo\node-ffi\src\ffi.cc(59): warning C4996: 'Nan::ForceSet': 被声明为已否决 [F:\test\eleDemo\node-ffi\build\ffi_bindings.vcxproj]
  f:\test\eledemo\node-ffi\src\ffi.cc(60): warning C4996: 'Nan::ForceSet': 被声明为已否决 [F:\test\eleDemo\node-ffi\build\ffi_bindings.vcxproj]
  f:\test\eledemo\node-ffi\src\ffi.cc(63): warning C4996: 'Nan::ForceSet': 被声明为已否决 [F:\test\eleDemo\node-ffi\build\ffi_bindings.vcxproj]
  f:\test\eledemo\node-ffi\src\ffi.cc(64): warning C4996: 'Nan::ForceSet': 被声明为已否决 [F:\test\eleDemo\node-ffi\build\ffi_bindings.vcxproj]
  f:\test\eledemo\node-ffi\src\ffi.cc(65): warning C4996: 'Nan::ForceSet': 被声明为已否决 [F:\test\eleDemo\node-ffi\build\ffi_bindings.vcxproj]
  f:\test\eledemo\node-ffi\src\ffi.cc(78): warning C4996: 'Nan::ForceSet': 被声明为已否决 [F:\test\eleDemo\node-ffi\build\ffi_bindings.vcxproj]
  f:\test\eledemo\node-ffi\src\ffi.cc(88): warning C4996: 'Nan::ForceSet': 被声明为已否决 [F:\test\eleDemo\node-ffi\build\ffi_bindings.vcxproj]
  f:\test\eledemo\node-ffi\src\ffi.cc(91): warning C4996: 'Nan::ForceSet': 被声明为已否决 [F:\test\eleDemo\node-ffi\build\ffi_bindings.vcxproj]
  f:\test\eledemo\node-ffi\src\ffi.cc(94): warning C4996: 'Nan::ForceSet': 被声明为已否决 [F:\test\eleDemo\node-ffi\build\ffi_bindings.vcxproj]
  f:\test\eledemo\node-ffi\src\ffi.cc(97): warning C4996: 'Nan::ForceSet': 被声明为已否决 [F:\test\eleDemo\node-ffi\build\ffi_bindings.vcxproj]
  f:\test\eledemo\node-ffi\src\ffi.cc(111): warning C4996: 'Nan::ForceSet': 被声明为已否决 [F:\test\eleDemo\node-ffi\build\ffi_bindings.vcxproj]
  f:\test\eledemo\node-ffi\src\ffi.cc(114): warning C4996: 'Nan::ForceSet': 被声明为已否决 [F:\test\eleDemo\node-ffi\build\ffi_bindings.vcxproj]
  f:\test\eledemo\node-ffi\src\ffi.cc(123): warning C4996: 'Nan::ForceSet': 被声明为已否决 [F:\test\eleDemo\node-ffi\build\ffi_bindings.vcxproj]
  f:\test\eledemo\node-ffi\src\ffi.cc(124): warning C4996: 'Nan::ForceSet': 被声明为已否决 [F:\test\eleDemo\node-ffi\build\ffi_bindings.vcxproj]
  f:\test\eledemo\node-ffi\src\ffi.cc(125): warning C4996: 'Nan::ForceSet': 被声明为已否决 [F:\test\eleDemo\node-ffi\build\ffi_bindings.vcxproj]
  f:\test\eledemo\node-ffi\src\ffi.cc(126): warning C4996: 'Nan::ForceSet': 被声明为已否决 [F:\test\eleDemo\node-ffi\build\ffi_bindings.vcxproj]
  f:\test\eledemo\node-ffi\src\ffi.cc(132): warning C4996: 'Nan::ForceSet': 被声明为已否决 [F:\test\eleDemo\node-ffi\build\ffi_bindings.vcxproj]
  f:\test\eledemo\node-ffi\src\ffi.cc(190): warning C4996: 'v8::Value::Uint32Value': 被声明为已否决 [F:\test\eleDemo\node-ffi\build\ffi_bindings.vcxproj]
  f:\test\eledemo\node-ffi\src\ffi.cc(191): warning C4996: 'v8::Value::ToObject': 被声明为已否决 [F:\test\eleDemo\node-ffi\build\ffi_bindings.vcxproj]
  f:\test\eledemo\node-ffi\src\ffi.cc(192): warning C4996: 'v8::Value::ToObject': 被声明为已否决 [F:\test\eleDemo\node-ffi\build\ffi_bindings.vcxproj]
  f:\test\eledemo\node-ffi\src\ffi.cc(193): warning C4996: 'v8::Value::Uint32Value': 被声明为已否决 [F:\test\eleDemo\node-ffi\build\ffi_bindings.vcxproj]
  f:\test\eledemo\node-ffi\src\ffi.cc(234): warning C4996: 'v8::Value::Uint32Value': 被声明为已否决 [F:\test\eleDemo\node-ffi\build\ffi_bindings.vcxproj]
  f:\test\eledemo\node-ffi\src\ffi.cc(235): warning C4996: 'v8::Value::Uint32Value': 被声明为已否决 [F:\test\eleDemo\node-ffi\build\ffi_bindings.vcxproj]
  f:\test\eledemo\node-ffi\src\ffi.cc(236): warning C4996: 'v8::Value::ToObject': 被声明为已否决 [F:\test\eleDemo\node-ffi\build\ffi_bindings.vcxproj]
  f:\test\eledemo\node-ffi\src\ffi.cc(237): warning C4996: 'v8::Value::ToObject': 被声明为已否决 [F:\test\eleDemo\node-ffi\build\ffi_bindings.vcxproj]
  f:\test\eledemo\node-ffi\src\ffi.cc(238): warning C4996: 'v8::Value::Uint32Value': 被声明为已否决 [F:\test\eleDemo\node-ffi\build\ffi_bindings.vcxproj]
  f:\test\eledemo\node-ffi\src\ffi.cc(265): warning C4996: 'v8::Value::ToObject': 被声明为已否决 [F:\test\eleDemo\node-ffi\build\ffi_bindings.vcxproj]
  f:\test\eledemo\node-ffi\src\ffi.cc(266): warning C4996: 'v8::Value::ToObject': 被声明为已否决 [F:\test\eleDemo\node-ffi\build\ffi_bindings.vcxproj]
  f:\test\eledemo\node-ffi\src\ffi.cc(267): warning C4996: 'v8::Value::ToObject': 被声明为已否决 [F:\test\eleDemo\node-ffi\build\ffi_bindings.vcxproj]
  f:\test\eledemo\node-ffi\src\ffi.cc(268): warning C4996: 'v8::Value::ToObject': 被声明为已否决 [F:\test\eleDemo\node-ffi\build\ffi_bindings.vcxproj]
  f:\test\eledemo\node-ffi\src\ffi.cc(307): warning C4996: 'v8::Value::ToObject': 被声明为已否决 [F:\test\eleDemo\node-ffi\build\ffi_bindings.vcxproj]
  f:\test\eledemo\node-ffi\src\ffi.cc(308): warning C4996: 'v8::Value::ToObject': 被声明为已否决 [F:\test\eleDemo\node-ffi\build\ffi_bindings.vcxproj]
  f:\test\eledemo\node-ffi\src\ffi.cc(309): warning C4996: 'v8::Value::ToObject': 被声明为已否决 [F:\test\eleDemo\node-ffi\build\ffi_bindings.vcxproj]
  f:\test\eledemo\node-ffi\src\ffi.cc(310): warning C4996: 'v8::Value::ToObject': 被声明为已否决 [F:\test\eleDemo\node-ffi\build\ffi_bindings.vcxproj]
  f:\test\eledemo\node-ffi\src\ffi.cc(367): warning C4996: 'Nan::Callback::Call': 被声明为已否决 [F:\test\eleDemo\node-ffi\build\ffi_bindings.vcxproj]

    42 个警告
    0 个错误

已用时间 00:00:10.36
gyp info ok

ShaMan123 · 2019-06-12T10:43:56Z

@bzoz don't know. windows-build-tools install?

bzoz · 2019-06-12T11:02:44Z

@ShaMan123 doesn't look like so, at least it does not add anything to the path for me. From the path I see you have also yarn installed, do you have any other node/npm build tools installed on your system?

ShaMan123 · 2019-06-12T12:00:10Z

not that I know of. npm, node, yarn.
but as I wrote in the second comment setting the environment variable fixes this.

bzoz · 2019-06-12T12:08:30Z

Ok, looks like when windows-build-tools is installing Python, it also adds those entries to the PATH. Thanks for your help!

ShaMan123 · 2019-06-12T12:09:53Z

happy to help

bnoordhuis · 2019-06-20T09:43:51Z

This was fixed in felixrieseberg/windows-build-tools#188 so I'll go ahead and close this out.

ShaMan123 changed the title ~~node-gyp cli error~~ wrong path to node-gyp bin May 23, 2019

ShaMan123 closed this as completed May 23, 2019

ShaMan123 reopened this May 23, 2019

bzoz mentioned this issue Jun 12, 2019

Fix setting up PATH environment variable felixrieseberg/windows-build-tools#188

Merged

bnoordhuis closed this as completed Jun 20, 2019

noseratio mentioned this issue Sep 12, 2019

node-gyp is unable to find msbuild if VS2019 is installed. #1663

Closed

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

wrong path to node-gyp bin #1760

wrong path to node-gyp bin #1760

ShaMan123 commented May 23, 2019 •

edited

ShaMan123 commented May 23, 2019 •

edited

NBSeven commented Jun 4, 2019 •

edited

NBSeven commented Jun 6, 2019

bzoz commented Jun 10, 2019

NBSeven commented Jun 10, 2019

bzoz commented Jun 10, 2019

NBSeven commented Jun 10, 2019

NBSeven commented Jun 10, 2019

bzoz commented Jun 10, 2019

NBSeven commented Jun 10, 2019

bzoz commented Jun 10, 2019

ShaMan123 commented Jun 11, 2019

bzoz commented Jun 12, 2019

bzoz commented Jun 12, 2019

NBSeven commented Jun 12, 2019

ShaMan123 commented Jun 12, 2019

bzoz commented Jun 12, 2019

ShaMan123 commented Jun 12, 2019 •

edited

bzoz commented Jun 12, 2019

ShaMan123 commented Jun 12, 2019

bnoordhuis commented Jun 20, 2019

wrong path to node-gyp bin #1760

wrong path to node-gyp bin #1760

Comments

ShaMan123 commented May 23, 2019 • edited

ShaMan123 commented May 23, 2019 • edited

NBSeven commented Jun 4, 2019 • edited

NBSeven commented Jun 6, 2019

bzoz commented Jun 10, 2019

NBSeven commented Jun 10, 2019

bzoz commented Jun 10, 2019

NBSeven commented Jun 10, 2019

NBSeven commented Jun 10, 2019

bzoz commented Jun 10, 2019

NBSeven commented Jun 10, 2019

bzoz commented Jun 10, 2019

ShaMan123 commented Jun 11, 2019

bzoz commented Jun 12, 2019

bzoz commented Jun 12, 2019

NBSeven commented Jun 12, 2019

ShaMan123 commented Jun 12, 2019

bzoz commented Jun 12, 2019

ShaMan123 commented Jun 12, 2019 • edited

bzoz commented Jun 12, 2019

ShaMan123 commented Jun 12, 2019

bnoordhuis commented Jun 20, 2019

ShaMan123 commented May 23, 2019 •

edited

ShaMan123 commented May 23, 2019 •

edited

NBSeven commented Jun 4, 2019 •

edited

ShaMan123 commented Jun 12, 2019 •

edited