You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is more a compatibility issue with the Node.js package and electron.js.
When running brainflow in an electron app, it\s working well in a dev env. But when packaging the app, electron cannot resolve the dll path in Boardshim constructor.
this.libPath=`${__dirname}/../brainflow/lib`;
Today, in order to solve this issue, we had to adapt brainflow a bit:
Welcome to BrainFlow project and thanks for your contribution! We will try to fix your issue ASAP. Make sure that you have read about issue format in the docs.
if (libs in current path exist)
load libs from it
else
try to load it wo path specification and then OS should search for it in current dir and in PATH/LD_LIBRARY_PATH env vars
I'm familiar with how this plays out using the BrainFlow Java library, and we've written some code in the Java binding to handle this. This may need a new contribution in the NodeJS binding or example code.
Describe the bug
This is more a compatibility issue with the Node.js package and electron.js.
When running brainflow in an electron app, it\s working well in a dev env. But when packaging the app, electron cannot resolve the dll path in
Boardshim
constructor.Today, in order to solve this issue, we had to adapt brainflow a bit:
To Reproduce
Install brainflow in an electron app. Create a button running an instance of synthetic board.
Run it locally, it will work.
Then, package the app and run it. Electron shoudl complain because it cannot resolve path to import dll files.
Info (please complete the following information):
pip list
command, for other languages please provide BrainFlow version usedExpected behavior
Path should be resolved properly in electron packaged context for production.
** suggestion **
Init constructor differently, or add an electron support.
The text was updated successfully, but these errors were encountered: