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.
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
installthat 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.