lsongdev / lsongdev/node-bluetooth

Travis test fail becaise of missing bluetooth.h

Open
#27 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
C++
Stars
205
Forks
56
PR merge metrics
No merged PRs in 30d

Description

I get `

node-bluetooth@1.2.5 install /home/travis/build/frankjoke/ioBroker.radar2/node_modules/node-bluetooth
node-gyp configure build
make: Entering directory /home/travis/build/frankjoke/ioBroker.radar2/node_modules/node-bluetooth/build' CXX(target) Release/obj.target/BluetoothSerialPort/src/linux/BluetoothSerialPort.o CXX(target) Release/obj.target/BluetoothSerialPort/src/linux/DeviceINQ.o ../src/linux/DeviceINQ.cc:35:37: fatal error: bluetooth/bluetooth.h: No such file or directory #include <bluetooth/bluetooth.h> ^ compilation terminated. make: *** [Release/obj.target/BluetoothSerialPort/src/linux/DeviceINQ.o] Error 1 make: Leaving directory /home/travis/build/frankjoke/ioBroker.radar2/node_modules/node-bluetooth/build'
gyp ERR! build error
gyp ERR! stack Error: make failed with exit code: 2`

errors and cannot test my package on Travis (for linuix) but on Raspian and Ubuntu install works.

The error is: /src/linux/DeviceINQ.cc:35:37: fatal error: bluetooth/bluetooth.h
and I could not find it as well.

On windows tester AppVeyor the installation works and all tests passes.

The effect started when I added your package to mine. If I remove the dependency it's installing fine.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the Linux build failure in src/linux/DeviceINQ.cc and inspect the Travis configuration and dependency setup around node-bluetooth. Reproduce the missing bluetooth/bluetooth.h error on Travis or an equivalent Linux environment, then verify that installation and the existing tests pass as they do on Ubuntu, Raspbian, and AppVeyor.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp, node.js
Domain
build-system, ci-cd, embedded-iot
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.