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
As mentioned in earlier issues, the limiting factor to freely updating NodeJS is the mraa library. By compiling the latest master, one would end up with NodeJS 18 with a working mraa installation, according to issue #512. There hasn't been a release based on Debian 12 and NodeJS, although that is near, according to #529.
The question now:
Can NodeJS 18 and the corresponding mraa be installed onto a V1.03 image? NodeJS itself can easily be updated on-target and everything will work fine, except mraa.
Can we somehow only compile mraa from the latest master and install that on a running target?
Will any conflicts arise because mraa was compiled for Debian 12 and the last release V1.03 is an older Debian version?
Do any other issues with this plan come to mind?
For gateways already in the field, it is either this or completely dropping GPIO, button and LED support, hence the question.
Thank you for your valuable input in advance.
The text was updated successfully, but these errors were encountered:
As mentioned in earlier issues, the limiting factor to freely updating NodeJS is the mraa library. By compiling the latest master, one would end up with NodeJS 18 with a working mraa installation, according to issue #512. There hasn't been a release based on Debian 12 and NodeJS, although that is near, according to #529.
The question now:
* **Can NodeJS 18 and the corresponding mraa be installed onto a V1.03 image?** NodeJS itself can easily be updated on-target and everything will work fine, except mraa.
Debian 12 and NodeJs 18 have been released since V01.04.01
* Can we somehow **only compile mraa** from the latest master and `install` that on a **running target**?
Yes, you can compile mraa with bitbake mraa and install the .deb file.
* Will any conflicts arise because mraa was compiled for Debian 12 and the last release V1.03 is an older Debian version?
We can't not guarantee the compatibility, I suggest you use our latest release which has Debian 12.
* Do any other issues with this plan come to mind?
For gateways already in the field, it is either this or completely dropping GPIO, button and LED support, hence the question.
As mentioned in earlier issues, the limiting factor to freely updating NodeJS is the mraa library. By compiling the latest master, one would end up with NodeJS 18 with a working mraa installation, according to issue #512. There hasn't been a release based on Debian 12 and NodeJS, although that is near, according to #529.
The question now:
Can NodeJS 18 and the corresponding mraa be installed onto a V1.03 image? NodeJS itself can easily be updated on-target and everything will work fine, except mraa.
Can we somehow only compile mraa from the latest master and
install
that on a running target?Will any conflicts arise because mraa was compiled for Debian 12 and the last release V1.03 is an older Debian version?
Do any other issues with this plan come to mind?
For gateways already in the field, it is either this or completely dropping GPIO, button and LED support, hence the question.
Thank you for your valuable input in advance.
The text was updated successfully, but these errors were encountered: