Home > GNOME > GNOME development – lack of progress report

GNOME development – lack of progress report

Well, it’s been a year since I said that I was going to get active on GNOME development again.

Perhaps that was over-optimistic.  Real Life™ did not go away and give me copious free time – and even snuck in a curveball or two.  Still, I haven’t been completely idle.

The original plan was to use the OMAP Zoom2 development platform to test GNOME using the ARM processor, with a further goal of exploring the OMAP video capability (ultimate motive: enable Cheese).  The Zoom II was made available by TI and provided by the GNOME Foundation.

The TI OMAP Zoom2 development system

The TI OMAP Zoom2 development system

This was going to be accomplished by using OpenEmbedded and Ångström to build GNOME for ARM.  As Ångström has Zoom2 support, this ought to have been simple.

In theory, at least.  In practice, I ran into the following obstacles:

  • I had not worked with git-based development before, and (at least at the time I started), and the latest-and-greatest pull were probably a bit more bleeding-edge than I should have started with.  No big deal there; standard teething troubles for trying to learn how to work with a new project.
  • Also at that time, one of the GNOME recipes had a build failure in it, and I was not yet familiar enough with OE and BitBake to fix it myself.
  • Working around that build failure, I discovered that my build system didn’t have sufficient disk space to hold a full OE build anyway.  (The OE documentation advises you to make sure you have “sufficient” system resources and bandwidth for a complete build, but is frustratingly non-specific about what qualifies as “sufficient”.)
  • This was about the time that my build system gave up the ghost anyway.
  • Poked at it a bit more with a borrowed build system that did have enough disk space.  That one died too.

Lessons learned:

  • Be more realistic about how much time I can squeeze in for GNOME projects, and remember to allow for life changing my schedule and commitments.
  • Do not underestimate the required beefiness of an OpenEmbedded build machine.
  • For OpenEmbedded development, stable branches might be your friend.

Plan B is now under consideration.

Categories: GNOME Tags:
  1. No comments yet.
  1. No trackbacks yet.