Building Arduino IDE 2.0 for Raspberry PI Ubuntu 64 bit

I have been experimenting with seeing if I could get the Arduino IDE 2 as well as CLI on a few of my SBC setups.

So far it works fine on my UP Squared board. But expected it would as it is an Intel Celeron processor.

Then decide to reset up my Raspberry PI 4 to run Ubuntu 22.04 off of SSD. From a previous thread (either here or on PJRC), that the RPI 64 bit builds are not yet automatically built... So can not pick up the current binaries from either the arduino.cc website nor from artifacts from recent github PRs...

So far the only place I know to get them are up from the github project:
koendv/arduino-ide-raspberrypi: arduino IDE v2 for raspberry pi (github.com)

And noted that the last release was 2.0.2 which I installed.
Note: initially the appimage file will not run as it depends on things that are not installed by default on Ubuntu 22.04

This is noted on the Readme file of the project, that you need to run the command:
sudo apt-get install libz1g-dev fuse libfuse-dev

however, this command fails as libz1g-dev does not exist.
I was able to get it to run using:
sudo apt-get install zlib1g-dev fuse libfuse-dev

So then decided to try to build my own copy of it, so clicked on the developers link:
arduino-ide-raspberrypi/README-DEVELOPER.md at main · koendv/arduino-ide-raspberrypi (github.com)

I was going to report I had problem in set up Docker - But it was user error. I was following the command lines in the code tags:

git clone https://github.com/koendv/docker-github-actions-runner

Which failed. Then figured out from above you mentioned to fork:

And so instead needed to use my github project not koendv

Note: the command:

./docker-github-actions-runner.sh

Failed to run, but it did run using sudo

Note: I set this up a week or two ago and it was failing each night as I think I setup the project back then but the RPI was not talking, so I reinstalled ubuntu and did everything from a clean install.

And it actually completed the last two runs. including:
https://github.com/KurtE/arduino-ide/actions/runs/3810372265
Which created the artifacts, which I was able to download the appimage version which ran.

However also today, I tried to resync up my main branch to be in sync the Arduino main branch,
(git reset --hard upstream/main) followed by (git push --force origin main)
And then reapplied the patch file and then tried to run it again with the current sources.
And that failed:

Not sure if I would need to (or should) delete my fork of arduino-ide, and then fork it again?

Or if, what the failure mentioned, maybe some tools changed and maybe need to update the patch file?
https://github.com/KurtE/arduino-ide/actions/runs/3813443441/jobs/6487191724#step:7:666

Thoughts?

The most important to understand when you are using GitHub Actions is that every component of the service and the supplemental services used by your workflow runs are subject to frequent transient outages. So you will get mysterious workflow run failures that are not caused by any problem in your project or workflow. Fortunately these transient outages usually resolve quickly. So when you encounter a failure that doesn't have a clear cause from within your repository, it is a good idea to try re-running the workflow. You can do that by clicking the "Re-run all jobs button at the top of the workflow run page.

As I mentioned above, it is possible this was just a temporary glitch, but from looking at the logs I am am suspicious that it might be caused by this change to the Arduino IDE project's build infrastructure:

That change was made after the 2.0.3 release.

I was concerned that the change might cause problems for community members building the IDE in their forks or locally, so I ran builds outside Arduino's repository when I was reviewing that pull request. I didn't have any problems, so I would suspect the problem is related to whatever adaptations koendv developed to build the IDE for Linux ARM host.

1 Like

Thanks, will try to rerun it again today.

I should mention that the first run that failed, the RPI was spewing out a lot of errors about writes failing, sort of like the old windows blue screen type errors. I ended up power cycling it as it was not responding to me.

Will first try to clear out anything temporary from the builds before I restart it.

Edit: Created an issue up on builds for RPI github...
Readme comments plus build problems - post build 2.0.3 · Issue #2 · koendv/arduino-ide-raspberrypi (github.com)

This topic was automatically closed 180 days after the last reply. New replies are no longer allowed.