I work at Intel Labs in a group called Open Design which has been developing tools for new creators and makers on the Galileo. As a person familiar with tools like NodeJS, Python, and Arduino -- but not familiar with the embedded Linux development process, I spent some time surfing around the forum and chatting with Sergey (who got the ball rolling for a full version of the LSB) and Alex (developers who use Galileo on their own time and have a deeper understanding of Embedded Linux) on the phone about getting an unofficial full build of Linux that we could use in our group for educational purposes.
It turns out understanding how to develop a useful build for people who are not Linux experts (like me) is not a trivial task and the efforts to create a Linux build that responds to the needs of this community and new developer communities have not been unified. To help explain this for people new to Galileo Dimitri Diakopoloulos has written a blog post called Navigating Linux on Galileo that outlines all the Linux versions that this community has been working on, the official full build, the Yocto, Poky, BSP build process, and some of the builds people have been posting on their blogs. So far this is the most comprehensive explanation I've seen out there.
Alex has been kind enough to collaborate with us over the last two weeks to incorporate the recipes he posted on his github site, increase the size of the SD card build to 2GB, and begin to add tools from my wish list (which I will include in a reply to this post later).
Here is the build Alex has posted on a VM I maintain with plenty of bandwidth: Download and Unzip it to your SD card.
In Alex's words the build includes:
- development tools (gcc, autotools set, and so on - everything Yocto's "tools-sdk" image feature implies, which is theoretically everything one should need to compile stuff);
- working sketch support (something other images don't have together with having dev tools enabled. I haven't yet tested that in full, but the daemons are there and behave normally, so it should work);
- git (which is not included into "tools-sdk");
- filesystem image size increased to 2GB;
in addition to the previously included
- USB sound kernel config;
- GSPCA PAC207 webcam support;
- node.js 0.10.25;
I haven't yet found the exact reason "pkgs-dev" image feature breaks the i2c and port expander, but let's see how your and my testing goes - it may be the case we don't really need all the *-dev packages at once for real life usages. Basic ones like uclibc-dev are installed already and other packages for specific needs (like opencv-dev) may be installed from the package repo - as simple as that.
Our hope is that people here can help us test and can post their wish list of tools that would be useful and features from the unofficial build might make their way into the official build as they find utility in the community - and that in doing so the build won't break the Arduino compatibility that is so useful to people familiar with the Arduino platform. (such as myself).
We have invited folks from design schools, electronics companies, hacker spaces, and creative technologists to download the build and provide feedback and our email threads are getting way to long - so I thought it would be useful to move the discussion to this forum and see if we can all collaborate and discuss. Right now Alex_T is the primary developer but if other folks here who are familiar with the build process can contribute their thoughts I'm excited to see what we can come up with.