Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Deasync Error: Could not locate the bindings file #15

Open
jordiblanchcarles opened this issue Jun 4, 2019 · 5 comments
Open

Deasync Error: Could not locate the bindings file #15

jordiblanchcarles opened this issue Jun 4, 2019 · 5 comments
Labels
bug enhancement research Need more information or research to understand or fix an issue
Milestone

Comments

@jordiblanchcarles
Copy link

Hello,

I'm trying to use cec-monitor within an ElectronJS v5.0.2 app, but the app is not starting because it throws an error while loading deasync module. Here it is the error thrown:

App threw an error during load
Error: Could not locate the bindings file. Tried:
→ /home/pi/cityadpro_player/node_modules/deasync/build/deasync.node
→ /home/pi/cityadpro_player/node_modules/deasync/build/Debug/deasync.node
→ /home/pi/cityadpro_player/node_modules/deasync/build/Release/deasync.node
→ /home/pi/cityadpro_player/node_modules/deasync/out/Debug/deasync.node
→ /home/pi/cityadpro_player/node_modules/deasync/Debug/deasync.node
→ /home/pi/cityadpro_player/node_modules/deasync/out/Release/deasync.node
→ /home/pi/cityadpro_player/node_modules/deasync/Release/deasync.node
→ /home/pi/cityadpro_player/node_modules/deasync/build/default/deasync.node
→ /home/pi/cityadpro_player/node_modules/deasync/compiled/12.0.0/linux/arm/deasync.node
at bindings (/home/pi/cityadpro_player/node_modules/bindings/bindings.js:88:9)
at Object. (/home/pi/cityadpro_player/node_modules/deasync/index.js:30:31)
at Module._compile (internal/modules/cjs/loader.js:808:30)
at Object.Module._extensions..js (internal/modules/cjs/loader.js:820:10)
at Module.load (internal/modules/cjs/loader.js:677:32)
at tryModuleLoad (internal/modules/cjs/loader.js:609:12)
at Function.Module._load (internal/modules/cjs/loader.js:601:3)
at Module.require (internal/modules/cjs/loader.js:715:19)
at require (internal/modules/cjs/helpers.js:14:16)
at Object. (/home/pi/cityadpro_player/node_modules/@senzil/cec-monitor/lib/cec-monitor.js:17:39)

Does anybody have any clue about how to solve this problem?

Thank you!

@pablodgonzalez
Copy link
Member

Deasync bindings are specific for the OS. So, It could be an issue with the Deasync version or maybe Deasync is not compatible with your OS. You should go to Deasync repo and check there or open an issue.

@jordiblanchcarles
Copy link
Author

It looks like ElectronJS and Deasync are not compatible. Is there any way to avoid using Deasync in cec-monitor?

@pablodgonzalez
Copy link
Member

Fork the library, remove de dependency and the functions where it is used.

@jordiblanchcarles
Copy link
Author

jordiblanchcarles commented Jun 6, 2019

Hello, I've already replaced the Deasync.loopWhile() method you were using with p-wait-for module's pWaitFor method to avoid deasync module, and it seems to be working properly.

Would you like to commit these changes?

@pablodgonzalez
Copy link
Member

Thanks @jordiblanchcarles We will check the changes and make performances test. By the way, in the future the main idea is make and node library to support the libcec without wrap the cec-client CLI because it is only for debugging and test.
Personally I don't know how to work ElectronJS with the bindinds.
I hope to make the tests soon.

@pablodgonzalez pablodgonzalez added bug enhancement research Need more information or research to understand or fix an issue labels Jun 25, 2019
@pablodgonzalez pablodgonzalez added this to the 2.2.0 milestone Jun 25, 2019
@pablodgonzalez pablodgonzalez pinned this issue Jun 25, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug enhancement research Need more information or research to understand or fix an issue
Projects
None yet
Development

No branches or pull requests

2 participants