Koen builds the official images. Now and again, I build images to make sure the process is reproducible. I’ve had an outstanding issue with building gnome-applets on Ubuntu 12.04 (Koen is using Fedora), but otherwise haven’t had issues reproducing the builds.
not building an angstrom image but i wanted to use OE to build a
basic image for my BBB as the basis for a couple upcoming embedded
linux classes, so i whipped this up:
If you uncompress the latest flasher image in http://beagleboard.org/latest-images, it looks like it creates a minimal root filesystem, the flashing utility (script?), and the rootfs tarball to be flashed to the eMMC’s linux partition:
cd build/
ls -AlF
-rw-r–r–. 1 root 358828968 Jun 20 04:16 Angstrom-Cloud9-IDE-GNOME-eglibc-ipk-v2012.12-beaglebone.rootfs.tar.gz
If I try the Angstrom build myself, using ‘MACHINE=beaglebone’ and bitbake target = ‘cloud9-gnome-image’, I get a file by the same name:
cd build/tmp-angstrom_v2012_12-eglibc/deploy/images/beaglebone
ls -AlF
-rw-r–r-- 1 jlf 340413308 Jun 27 21:31 Angstrom-Cloud9-IDE-GNOME-eglibc-ipk-v2012.12-beaglebone.rootfs.tar.gz
The 2 rootfs tarballs seem to fairly close in size. Does this mean I’m doing it right?
Does this mean the BBW and BBB use the same rootfs?
Can someone please confirm the MACHINE and bitbake target used?
You’re basically correct and I do what you’ve suggested to produce builds myself. I did however have to move to using Fedora to build that image. I could build the kernel no problem in ubuntu though.