Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [mraa-dev] Cannot compile on raspberryPi4, python3.13, swig4.5.1 ready to help

Many Thanks Alex for your answer,

I’ll go back to github and follow the activity there. I have read somewhere that the way mraa interacts with the GPIO has to evolve, which seems to be hard work and far beyond my capabilities.

At least I can make compilation tests on raspberry Pi 3 and 4 (maybe 5 from january if father christmas is kind enough to deliver one) with debian raspberryPI OS and PiOS then report if needed.

From my outsider point of view there are three axes that need efforts :

  • cleaning all remainings of python2 dependencies in the code, even if compilation goes through smoothly it might be a source of weird errors

  • moving to swig version 4, 4.5.1 is out since september

  • rejuvenate _javascript_ use, with nvm it is easy to focus on a given recent version to avoid the fast evolution of version.

Do not hesitate to call on me if I can contribute for simple things.

Cheers

Gérard

Le 27/10/2026 à 15:47, Alex T via mraa-dev a écrit :


On Tue, Oct 20, 2026 at 3:04 PM vidal gerard via mraa-dev <mraa-dev@xxxxxxxxxxx> wrote:

Hi all,

First of all I am not a dev but I am ready to help with my limited skills. I deadly need mraa and upm because I have a large library of codes in jupyter notebooks developed on raspi to interact with leds, sensors, motors,… All those “assets” have been abandoned for 3 years and as I am retired I would like to bring them back to life and share out of the academic world for public education.

Compilation of mraa fails with errors I am not able to solve and I have also spotted some intrinsic problems that may prevent smooth compilation

<snip> 

I do not want to overload this first mail but I have listed error messages, observations and some (failed) workarounds that I can provide if that helps. I can test proposals and write code (with guidance).

I hope mraa is not dead.

Hi Gérard,

It's not dead, just not very active either and has been on kind of hiatus for quite a few years. Tom and I have started reviving it late last year and it progresses, albeit slowly as "real life" gets in the way.

The UPM might not be building right now, that's expected - we are focusing on MRAA, as the foundation, first. That one builds and passes basic tests on Ubuntu 24.04 (see the Github CI/Actions in the repo, if interested), though I expect there to be more issues to iron out, as some of the kernel interfaces MRAA relies upon have changed over years. I plan to look into that after getting the basics like builds, tests, and some of my local debug infra up to speed. I haven't tried building on Debian so far.

While using the mailing list is fine, I'd encourage you to use Github issues to report specific problems you're observing, with logs and such, as it may be more convenient due to all the integrations there are (e.g., code references). Start with MRAA first and after that one is building and working, we can take a look at the UPM part of it.

cheers,
Alex

_______________________________________________
mraa-dev mailing list
mraa-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/mraa-dev


Back to the top