node-bluetooth causing build error
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 30/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- cpp, nodejs
- Domain
- build-system, embedded-iot, operating-systems
Research direction
Start by reproducing the node-bluetooth@1.2.6 install in the reported Windows 10, Node v12.9.1, Python 2.7, Visual Studio 2019, and node-gyp v5.0.3 environment. Inspect the node-gyp configure/build output from the node_modules\node-bluetooth directory and determine what prevents the build from completing; done means the module installs without the reported build error.
Written by the indexing model from the issue text.
Description
Environments :
- Windows 10 version 1903
- Visual Studio Enterprise 2019
- Python 2.7
- node v12.9.1
- node-gyp v5.0.3
The problem
I was trying to use ESCPOS_2.5.2 when node-gyp start building the ( node-bluetooth ) module, warnings and errors start to pop on the console till
gyp ERR! build error
gyp ERR! stack Error: "C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\MSBuild\Current\Bin\MSBuild.exe" failed with exit code: 1
gyp ERR! stack at ChildProcess.onExit (C:\Users\xxxx\AppData\Roaming\npm\node_modules\node-gyp\lib\build.js:196:23)
gyp ERR! stack at ChildProcess.emit (events.js:209:13)
gyp ERR! stack at Process.ChildProcess._handle.onexit (internal/child_process.js:272:12)
gyp ERR! System Windows_NT 10.0.18362
gyp ERR! command "C:\Program Files\nodejs\node.exe" "C:\Users\xxxx\AppData\Roaming\npm\node_modules\node-gyp\bin\node-gyp.js" "configure" "build"
gyp ERR! cwd D:_Node_field\pos_printer\node_modules\node-bluetooth
gyp ERR! node -v v12.9.1
gyp ERR! node-gyp -v v5.0.3
gyp ERR! not ok
npm WARN pos_printer@1.0.0 No repository field.
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: node-bluetooth@1.2.6 (node_modules\node-bluetooth):
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: node-bluetooth@1.2.6 install:node-gyp configure build
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: Exit status
is something with the environment causing the problem?
- Dominant language
- C++
- Stars
- 205
- Forks
- 56
- PR merge metrics
- No merged PRs in 30d
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from lsongdev/node-bluetooth
-
bug
Difficulty 4/5 3-5 days Newbie friendliness 45/100
lsongdev/node-bluetooth#61 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 25/100
lsongdev/node-bluetooth#60 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 30/100
lsongdev/node-bluetooth#57 · 1 comment · 2 reactions ·
-
Maintenance status? Open
Difficulty 1/5 Under an hour Newbie friendliness 10/100
lsongdev/node-bluetooth#55 · 8 comments ·
-
Battery status? Open
Difficulty 5/5 Over a week Newbie friendliness 20/100
lsongdev/node-bluetooth#54 · 1 comment ·
All issues in lsongdev/node-bluetooth
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
duckdb/duckdb-wasm#2258 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
objectionary/eo-graphs#75 ·
-
Coarray integration tests carry no LABELS, so run_tests.py silently skips them under every backend Opencoarray
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
FISCO-BCOS/FISCO-BCOS#5642 ·